RARE user and assistance email list

["Tim Chown via groups.io" <>]

Repeating what I posted elsewhere….

Hi Csaba,

Getting new routing protocols published as full RFCs can be quite a time 
consuming and long task, requiring a lot of patience.

I think there’s a good argument for documenting your protocols, and if you’re 
doing that doing it as an Internet Draft (I-D) is a useful format, because it 
should vey precisely specify the protocol, and allow others to write 
interoperable implementations.  And regardless you’d also have a very useful 
reference for the protocols.

Note that for such a draft/drafts to be published as an RFC, you’d either 
need it/them adopted by an IETF WG and pushed through to publication that 
way, by WG consensus, or you’d have to use the Individual Submission route, 
which can be slow.  

I don’t know the details of your protocols to know how many pages of an I-D 
would be needed to specify them, and thus how much work it would be.  As 
classic ‘command-response’ protocols you might look at SMTP or similar RFCs 
to gauge that.

You could try to present the protocols in the general Routing Area WG of the 
IETF, e.g. they met at IETF112 with this agenda:
https://datatracker.ietf.org/meeting/112/materials/agenda-112-rtgwg-04
But as you can see, to present, you really need a draft.
You could anyway contact the two chairs, listed in that agenda, for advice.  
Say these protocols are used in your open source project, and you’re 
interested in documenting them for re-use.

There are 23 routing WGs (including bier!), see 
https://datatracker.ietf.org/wg/, maybe lsr/lsvr are relevant.

But again, even if you don’t follow the RFC path, a well written I-D could 
still help other people implement your protocols.

There is always an aspect in adopting a draft that the new draft should 
provide something existing protocols do not.   Perhaps it being more 
“disagnostisable” is an argument, though I’m not sure it’s a real English 
word, but I know what you mean by it :)

Tim

> On 7 Dec 2021, at 09:28, mc36 <> wrote:
> 
> 
> 
> 
> -------- Forwarded Message --------
> Subject: drafts about freerouter specific igps...
> Date: Tue, 7 Dec 2021 10:27:25 +0100
> From: mc36 <>
> Reply-To: 
> To: Tim Chown <>, Moh  csi J  nos 
> <>
> CC:  
> <>
> 
> hi,
> so freerouter have two home-grown igp protocols: http://lsrp.nop.hu and 
> http://pvrp.nop.hu ...
> both are pure text based protocols like the old ones, smtp/pop3/imap/http, 
> to ease troubleshooting...
> both operate over udp for discovery and tcp for the session...
> both send a loot of extra info in open/update messages like hostnames, 
> interface names,
> software version, and the standard things like addresses, bandwidths, 
> delays...
> lsrp is a simplified link state protocol, much like single-area/level 
> ospf/isis...
> pvrp is a path vector protocol, much like bgp is, with traversed routerid 
> list, instead of aspath...
> they evolved a lot, and nowadays have very fancy, sdn-alike features like 
> dynamic metrics...
> in the example below, you can spot that in my 3 vpn concentrator overlay 
> setup, it outperforms internet rtt easily! :)
> the question for you, as rfc writers i know, what's your opinion, how hard 
> would it be to have these documented and ietf?
> thanks,
> cs
> 
> 
> noti#ping vpn.nop.hu
> pinging 2a03:a140:10:2961::cc1e:c0de, src=2001:db8:1101::11, vrf=inet, 
> cnt=5, len=64, tim=1000, gap=0, ttl=255, tos=0, flow=0, fill=0, 
> sweep=false, multi=false, detail=false
> !!!!!
> result=100%, recv/sent/lost/err=5/5/0/0, rtt min/avg/max/sum=37/37/38/186, 
> ttl min/avg/max=239/239/239
> noti#ping vpn.net.nop.hu
> pinging 2001:db8:1101::180, src=2001:db8:1101::11, vrf=inet, cnt=5, len=64, 
> tim=1000, gap=0, ttl=255, tos=0, flow=0, fill=0, sweep=false, multi=false, 
> detail=false
> !!!!!
> result=100%, recv/sent/lost/err=5/5/0/0, rtt min/avg/max/sum=31/31/32/157, 
> ttl min/avg/max=254/254/254
> noti#
> 
> 
> 
> 
> 



-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#100): https://groups.io/g/freertr/message/100
Mute This Topic: https://groups.io/mt/87562384/6413194
Group Owner: 
Unsubscribe: https://groups.io/g/freertr/unsub []
-=-=-=-=-=-=-=-=-=-=-=-