Re: [hackathon] Coding a custom data link or network layer protocol

8218kelmo katerega micheal <8218kelmo@gmail.com> Sat, 05 November 2022 07:24 UTC

Return-Path: <8218kelmo@gmail.com>
X-Original-To: hackathon@ietfa.amsl.com
Delivered-To: hackathon@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B4C81C14CEFC for <hackathon@ietfa.amsl.com>; Sat, 5 Nov 2022 00:24:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.124
X-Spam-Level:
X-Spam-Status: No, score=-0.124 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, FROM_STARTS_WITH_NUMS=0.738, HTML_MESSAGE=0.001, NORMAL_HTTP_TO_IP=0.001, NUMERIC_HTTP_ADDR=1.242, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4vczwwLt2wPc for <hackathon@ietfa.amsl.com>; Sat, 5 Nov 2022 00:24:43 -0700 (PDT)
Received: from mail-lj1-x234.google.com (mail-lj1-x234.google.com [IPv6:2a00:1450:4864:20::234]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 462E6C14F75F for <hackathon@ietf.org>; Sat, 5 Nov 2022 00:24:43 -0700 (PDT)
Received: by mail-lj1-x234.google.com with SMTP id k19so9270100lji.2 for <hackathon@ietf.org>; Sat, 05 Nov 2022 00:24:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=2OxnlaSoYIZRGyC7l+Wthx7sH8E/IFlMNKyEega5HYw=; b=NnpAUe7zeWCs3VOEBTx0xgJrk9U8twXnEpoR0f5g7XVtWkeZ03zrOBA3JM6tJb/r9x dq4Yo6+t3dEH6C/YxkYmN1gQ6vH5Tapj0D+bcTmdSAeXzH5g/Gk7KxeZLlWz79jVlsDw 5iXdrWT0taAq7cMjOg4ILQSWCu4zMtQQBeSpz4g1l3ZdLFmTWdQYAHuRxOFljeNYE5rJ mYzTFLGQ8JsYq0gnSjubvruKajQTDC6UcUEfeAB1ODYDMdYp/v/TDDrm1KfQ3MdMCmJl xGuS5RCKBqcER7d8VOP5YpPauxPhfSCfCmeRn3NPAnbIci70BKLZR3BDPSt0E4sLOBF7 yrYQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=2OxnlaSoYIZRGyC7l+Wthx7sH8E/IFlMNKyEega5HYw=; b=RLZan0zc678GsZqMN23oHP8LUi4WB0CQCdHduAOlSROZT6FKUMeImzyx20rhYt2dKg G61rGG7CxTWvzuXhnQTqZsfJKBbhQZhJqtbYs6XJsmmiEKN3EhIhM4KcAXha2r257HQm ZR04qi2ZRurXbDQUIqBPE0a/iYmLl4r7GjcaNxSmR7Jy/5gG/MZpdv9TAkPKxW1W5riN 7wabOYAQHklZQmZap49Xj2KyUMBAdwNtF4aM5yyjWBcfWlZ7lml80eFGxsnMdKNT8f4U e77J067NDt98gyfHu6y5rKjf0Fs/pXNTV+MY+5ExPAmkbzll0KIGZoPi/S5UuZ194zRD gJBA==
X-Gm-Message-State: ACrzQf2zr6cRB0qLfwnu20zN5XK7YVsuCK82xx/hxI6nDoSUUaSf1s7z KTVRwT9fycSfx9fxGi5ECGaWRRuGeVmgKyuzhg==
X-Google-Smtp-Source: AMsMyM4IGDgtob/YNhtZeYg6Tnkd8/R+EL01sya1C31X1Jp1xliObXuRTJsbWVeV7TIEHGV8kITzcO4NWxvxHeyZMfo=
X-Received: by 2002:a2e:a4c3:0:b0:277:4d09:9870 with SMTP id p3-20020a2ea4c3000000b002774d099870mr11785784ljm.98.1667633080833; Sat, 05 Nov 2022 00:24:40 -0700 (PDT)
MIME-Version: 1.0
References: <CAB_544W7j+m8Paa0JtYD=faQsRMgHa4TfTK+aCT_qGBzodLB7Q@mail.gmail.com> <CA+syWAN4g5ittSCukb3N3wfRNy+sv9jBd6h5D4R1Kp+r4yJ2Rg@mail.gmail.com>
In-Reply-To: <CA+syWAN4g5ittSCukb3N3wfRNy+sv9jBd6h5D4R1Kp+r4yJ2Rg@mail.gmail.com>
From: 8218kelmo katerega micheal <8218kelmo@gmail.com>
Date: Sat, 05 Nov 2022 06:20:56 -0400
Message-ID: <CAB_544WbFn7jWGzQSWt8RNSgrRy6kwFX393zFSzyTh8xzzT+YA@mail.gmail.com>
To: guest271314 <guest271314@gmail.com>
Cc: hackathon@ietf.org
Content-Type: multipart/alternative; boundary="000000000000661b7005ecb41508"
Archived-At: <https://mailarchive.ietf.org/arch/msg/hackathon/HTB8saEBORxEpjN2YGETrcPjX2U>
Subject: Re: [hackathon] Coding a custom data link or network layer protocol
X-BeenThere: hackathon@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "Discussion regarding past, present, and future IETF hackathons." <hackathon.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/hackathon>, <mailto:hackathon-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/hackathon/>
List-Post: <mailto:hackathon@ietf.org>
List-Help: <mailto:hackathon-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/hackathon>, <mailto:hackathon-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 05 Nov 2022 07:24:47 -0000

I’m Sean with the NOC. We don’t have a boilerplate other than what we
provide for the network. The IETF uses 2001:67c:370::/48 and
2001:67c:1230::/46 for IPv6 and 31.133.128.0/18 and 31.130.224.0/20 for
IPv4. We supply bandwidth for the conference space and venue hotel guest
rooms. IPv4 addresses are provided by DHCP and Stateless Auto-configuration
for IPv6 (SLAAC). If you could let us know what your protocol number is,
that would benefit if we see some oddness or issues on the network.

Sean and the NOC Team

Hi Sean, we are at internet draft level, hoow do we get a protocol number?


I think it will be difficult to respond seriously without further
details. At what layer will this protocol be? 2? 3? 7? Since you
mention custom _frames_, I assume it will be a completely new stack,
from layer 2 to the applications?

the protocol is at layer 2 and 3 (they are actually two protocols ie one on
layer2 another on layer 3) and yes the custom frames are generated at
layer2 and the protocol at layer 3 generates custom packets


IETF works on the TCP/IP family, so, if your protocol is not IP, no,
there is no document from IETF.

from layer3 upwards it implements and extends TCP so i think that qualifies
it to be IP, maybe correct me if am wrong on that one, thanks alot


If you want it to work across the Internet, does it mean it is a
layer-7 protocol, intended to work over IP and one of its usual
transports? If it is not IP (v4 or v6), there is no chance it will
work on the Internet. (Of course, you can always tunnel it over IP
between two end-poinst that you control.)

To summarize: details needed.
its not a layer 7 protocol, its layer 2 and layer3 while using extended TCP
over IP (v4 or v6)




And, likely, the answer is that you should read:

https://www.goodreads.com/book/show/505561.Internetworking_with_TCP_IP_Vol_1

https://www.goodreads.com/book/show/194839.Internetworking_with_Tcp_Ip_Vol_III

     am still looking into the links thanks for sharing i do appreciate,
 though founf this otherone as well i dont know if its just the new verison
of it or i stick with the above two first
https://www.amazon.com/Internetworking-TCP-IP-One-6th-dp-013608530X/dp/013608530X/ref=dp_ob_title_bk
173usd

     Have you looked into WebTransport?

     Yes, I have looked into webTransport but the problem i had with it was
it doesn't give enough flexibility to implement logic over layer 2. because
the custom protocol at layer 2 has implementation with flow almost similar
to the logical link layer






On Fri, 4 Nov 2022 at 20:51, guest271314 <guest271314@gmail.com> wrote:

> Have you looked into WebTransport?
>
> On Tue, Nov 1, 2022 at 5:21 AM 8218kelmo katerega micheal <
> 8218kelmo@gmail.com> wrote:
>
>> hi
>> am micheal and am working on some project where i have to create a custom
>> protocol with custom packets and custom frames
>> is there some boilerplate code or sample code orany guiding documents
>> from ietf that can enable me do that.
>>
>> i have so far managed to create the custom packets and custom frames but
>> how do it make them recognizable across the global internet
>> infrastructure and network?
>>
>> _______________________________________________
>> hackathon mailing list
>> hackathon@ietf.org
>> https://www.ietf.org/mailman/listinfo/hackathon
>> Unsubscribe: mailto:hackathon-request@ietf.org?subject=unsubscribe
>>
>