Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: "David P. Reed" <dpreed@deepplum.com>
To: "Dave Taht" <dave.taht@gmail.com>
Cc: "cerowrt-devel" <cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] 5g nas protocol
Date: Sun, 19 Jan 2020 22:40:39 -0500 (EST)	[thread overview]
Message-ID: <1579491639.979315009@apps.rackspace.com> (raw)
In-Reply-To: <CAA93jw5dtWmOq8HrHzAEDWSoUVLCgK_YVn5MQ1KE9SyQMJVo-A@mail.gmail.com>

What a beautiful document. I noticed a few bugs in the protocol here and there as I skimmed it, and what appear to just be typos.

I'm sure it all just works perfectly, after reading the proof of correctness that I found on github.

:-(

On Sunday, January 19, 2020 8:54am, "Dave Taht" <dave.taht@gmail.com> said:

> If anyone out there is having trouble sleeping, I highly recommend
> trying to make heads or tails of the 3gpp nas protocol which governs
> how user equipment connects and moves about it. I got as far as sec
> 6.2.5.1.1.2.
> 
> https://www.etsi.org/deliver/etsi_ts/124500_124599/124501/15.00.00_60/ts_124501v150000p.pdf
> 
> --
> Make Music, Not War
> 
> Dave Täht
> CTO, TekLibre, LLC
> http://www.teklibre.com
> Tel: 1-831-435-0729
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel
> 



      reply	other threads:[~2020-01-20  3:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-19 13:54 Dave Taht
2020-01-20  3:40 ` David P. Reed [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1579491639.979315009@apps.rackspace.com \
    --to=dpreed@deepplum.com \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=dave.taht@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox