Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Denis Ovsienko <infrastation@yandex.ru>
To: cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>
Subject: [Cerowrt-devel] Fwd: [Babel-users] time for feedback (Babel authentication goes I-D)
Date: Mon, 27 Aug 2012 16:41:45 +0400	[thread overview]
Message-ID: <2214841346071305@web7f.yandex.ru> (raw)

Hello, list.

Since CeroWrt is closely related to the Babel authenticatin mechanism and since all potentially interested babel-users readers seem to be on vacations, I find it right to forward this update to cerowrt-devel. Feedback is welcome through any of the lists or in private. Thanks.

-------- Beginning of forwarded message  --------
20.08.2012, 19:46, "Denis Ovsienko" <infrastation@yandex.ru>:

Hello, list.

As some of you remember, in late May I suggested a sketch of a Babel authentication mechanism, intending to develop it into a more formal specification later. A prototype implementation became available in early June, the next step was writing a proper specification. That's what I've been busy doing for last two months, and today I would like to share the result, which is the very first (00) version of the Babel authentication Internet-Draft (I-D):

http://tools.ietf.org/html/draft-ovsienko-babel-hmac-authentication-00

The document is just 40 pages long. Just to remind, the "draft" relates to the publication series, not necessary to the document quality. This I-D hopefully incorporates all the background, technical information and justification necessary to understand, implement and use this authentication mechanism. I am basically asking to show where I am wrong in this assumption. I need your feedback and reviews to understand how much finished it is.

Is there anything that is written really bad? Anything that should be added or removed? Feedback of first-time readers is even more welcome. If you understand Babel but not the authentication, that's not a problem, the I-D is self-contained. It's not? Let everyone know! Please send your comments to the mailing list.

Cheers.

Special notes to Juliusz.

1. Section 4.1 was written to address the encoding concerns, tell me if it does this job. May be some of the arguments didn't make it from my head to the paper, I will fix it then.

2. The current document works off the current "no IANA registry" situation. If you prefer creating an IANA registry for Babel TLV types, let me know and I will update the document respectively. I can post a draft registry description, if you want.

--
    Denis Ovsienko

_______________________________________________
Babel-users mailing list
Babel-users@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/babel-users
-------- End of forwarded message --------

-- 
    Denis Ovsienko

                 reply	other threads:[~2012-08-27 12:41 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=2214841346071305@web7f.yandex.ru \
    --to=infrastation@yandex.ru \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    /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