L7 protocol design

Philippe Duke <philippe46@netassist.ua> Wed, 28 December 2016 09:57 UTC

Return-Path: <philippe46@netassist.ua>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 73F34129431 for <ietf@ietfa.amsl.com>; Wed, 28 Dec 2016 01:57:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.001
X-Spam-Level:
X-Spam-Status: No, score=-5.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-3.1, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8QbCyzag-ovp for <ietf@ietfa.amsl.com>; Wed, 28 Dec 2016 01:57:43 -0800 (PST)
Received: from mail.netassist.ua (mail.netassist.ua [IPv6:2001:67c:1874:5::2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3EFDA128AB0 for <ietf@ietf.org>; Wed, 28 Dec 2016 01:57:43 -0800 (PST)
Received: from [213.160.157.104] (helo=[10.6.0.46]) by mail.netassist.ua with esmtpsa (TLSv1.2:DHE-RSA-AES128-SHA:128) (Exim 4.85 and XAMS 0.0.13) id 1cMBHx-0007z0-92 for ietf@ietf.org; Wed, 28 Dec 2016 12:16:53 +0200
To: ietf@ietf.org
From: Philippe Duke <philippe46@netassist.ua>
Subject: L7 protocol design
Organization: NetAssist LLC
Message-ID: <8f94c005-e27f-c81f-01e5-8ae4dea66f79@netassist.ua>
Date: Wed, 28 Dec 2016 11:57:40 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Icedove/45.5.1
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/AFY2apzE8jIIpzZLvoYdUg0dQs0>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 28 Dec 2016 09:57:45 -0000

Hello, dear IETF community. I would like to develop L7 protocol for my
application and public documentation about it. Good protocol development
is quite difficult stage, but not a problem. But at the same time, I
don't have any experience writing protocol documentations (RFC's).

What guidelines do you have?

Is the RFC 4253 (SSH) good example of document design? Should I follow
same principle?


Please give me some examples how to make it correct. Even examples of
very simple protocols.

What I need as requirements:

    TCP/UDP transport

    Authentication

    Encryption

    Sequence control

My protocol would carry small status messages like (10-20 bytes with
timestamps and some sort of sequence synchronization).


Thank you very much for your answers. Sorry for posting into the general
list.

-- 
Philippe Duke
Network software engineer
System-level developer

NetAssist LLC
Ukraine
Khreshchatyk Street, 10B, office 8
AS29632

http://netassist.ua
Our GitHub Repository:
https://github.com/netassist-ua