Is it time for a revolution?

We state that – the authors co-signed write this in their own capacities, and the questions posed below and the thoughts behind them are those of the authors and any individual or organization that chooses to explicitly back our position here, and should not be attributed otherwise.

There comes a time in everyone’s life when they look at the status quo and ask: is what is currently occurring for the good of the collective, or is it merely serving the interests of a single dominant player? Dependent on the answer to that question, the question must then be asked – is it time to force a change?

This is the question we find ourselves asking with regards to the IETF. Over the last few years, we have seen the landscape in the routing field dominated entirely by one vendor. This has led to forcing every other IETF contributor to play their tune whenever that one vendor has a stake, or risk having their proposals being left to wither on the vine. There are several examples of this; it has become endemic in the SPRING working group; we see similar happening elsewhere in the IETF. We are concerned that it will be only a matter of time before we see this behavior creeping into the IDR, LSR and other working groups. It seems that the will of the operators/other vendors is being left behind.

And so – while we are not going to go into specifics – because enough has been written and said in so many forums already – we are going to ask the rest of the vendors, yes, we are looking at you Juniper, Huawei, Nokia, Ericsson, ZTE, and so the list continues – are you content to continue to have your future, and the future of your customers dictated by one vendor in the routing space?

To the operators, both big and small, are you prepared to let your tomorrow be dictated by the whims of a single vendor? Where thoughts and ideas are all entirely dictated by one vendor in the routing space? Are you prepared to have your own innovation hampered or otherwise ignored unless you can get the buy in of ONE vendor? Are you ready to admit it?

We need to ask ourselves a simple question – are we content with the current situation in the IETF? Is it time for us to say enough is enough and demand a standards revolution? We leave that to each reader to decide.

The undersigned believe that the time has come to say enough is enough! The Internet we know today was built from the bottom up which is precisely the approach we need to return to, instead of the interests of a single vendor based on their stock performance on the Nasdaq.

Andrew Alston

Sander Steffann

Fernando Gont

Jan Zorz

 

 

James Stapley

Senior Network Engineer at Nephos Technologies

4 年

Dissatisfaction with the IETF goes back a ways... https://archive.psg.com/051000.sigcomm-ivtf.pdf

回复
Vanessa De Oliveira Mello

Software Engineer | Itaú Unibanco | 2x AWS Certified | Java | SpringBoot | Golang

4 年
回复
Marc Edwards

Information/Operations Technologist. Network, Data Center, and Cyber Security.

4 年

Fork it

回复
Luis B.

Peering & Interconnect Specialist, Internet Veteran, IPv6 Evangelist

4 年

And when a small company or an individual tries to venture in the process of standardisation it's flooded with legal threats and patents violations from the big ones.

Dave Taht

@dtaht:matrix.org - Truly speeding up the Net, one smart ISP at a time

4 年

I note that I have essentially quit the ietf for a multitude of other reasons. I believe in running code far more than standards, and I've hit a wall in the SCE vs L4S fight that I don't think will ever be resolved there. It took a weekend to write fq_codel, and 6 years to standardize it at RFC8290. Babel and homenet... don't get me started. Most of what the ietf does is kind of obsolete. If it never meets again, I'm not sure if anyone would miss it. That said, I don't know what to replace it with.

要查看或添加评论,请登录

Andrew Alston的更多文章

  • A Sad farewell to one chapter, and on to the next

    A Sad farewell to one chapter, and on to the next

    Today I was informed that I was starting my notice period and would be saying goodbye to Liquid, and it’s been an…

    26 条评论
  • Is Political Correctness Hurting us all?

    Is Political Correctness Hurting us all?

    What I write here is probably going to get me flamed - but - so be it, it's time for me to not be politically correct…

    4 条评论
  • A Rebuttal to the NRO's letter to the Mauritian Government.

    A Rebuttal to the NRO's letter to the Mauritian Government.

    What follows below is the text of an open letter that I have just requested be dispatched the Honourable Chief Justice…

    86 条评论
  • Non-Standard Standards (SRv6)

    Non-Standard Standards (SRv6)

    I was informed that certain people were having problems reading the article on medium because of the article limit - so…

  • When it comes time to appeal...

    When it comes time to appeal...

    Today Fernando Gont, Sander Steffann and I, acting in our personal capacities, launched a formal appeal against actions…

    2 条评论
  • RPKI – The things that are not being considered.

    RPKI – The things that are not being considered.

    So, firstly let me start by stating that I would love a secure internet – all of us want security in our lives – none…

    21 条评论
  • The IETF - A follow up to the revolution article

    The IETF - A follow up to the revolution article

    As per the previous article I published, the thoughts contained here-in are my own and should not be attributed to any…

    6 条评论
  • SRv6+ - A followup article

    SRv6+ - A followup article

    So, following my post a few months ago about why we wanted SRv6+ - and having become fairly actively involved in the…

    5 条评论
  • Dealing with SR-TE Quirks

    Dealing with SR-TE Quirks

    While doing some more in depth testing with Segment Routing - we have run into a few issues with regards to…

  • Teaching networking through code...

    Teaching networking through code...

    So, yesterday I asked one of my team to write me a BGP SR-TE injection daemon. Now, the individual concerned is a very…

    9 条评论

社区洞察

其他会员也浏览了