Rare project developers

[Tim Chown <>]

Hi Simon,

That all sounds good, thank you.   Could you write a paragraph or two that we 
can send to Tryfon for his weekly newsletter to advertise this to other 
NRENs.   It might be something worth pointing out in SIG-NOC too?  But really 
we need to hit new audiences - I wonder which IETF WG lists would be 
best-suited?   Is there a hackathon mail list?  I must register for it :)

Tim

> On 15 Feb 2022, at 17:58, Simon Leinen <> wrote:
> 
> Tim Chown writes:
>> I think the format of the draft doc is good.
> 
> thanks for reviewing!
> 
>> Simon, how do we publish this, with more info about the platform, and
>> encourage / allow others to contribute ideas?
> 
> My idea was to publish the "projects" part to the Hackathon Wiki.  In
> fact I did this just now, because we definitely have enough material,
> and we can always change things later if necessary.
> 
> The remainder of the document can be used for our own planning.
> 
> I have added a list of (known) participants - please add yourselves!
> 
> And I have added some "next steps" that we should work on before the
> hackathon.  Please have a look.
> 
> My main worry is that we find a way to make remote participants feel
> included.  I suggest we try to use the Gather platform that the IETF
> (including Hackathon) uses.  Maybe we could have our next meeting there
> as an exercise?  https://app.gather.town/app/L4fNNdm1NJa1sE2v/ietf
> (password: "notewell")
> 
> Another question is whether we should use the "Hacknet"
> (https://hacknet.meeting.ietf.org/) for L2 VPN connectivity.  I guess it
> could be useful.  So far only Mikrotik devices seem to be supported.
> (Maybe a (meta-) Hackathon project would be to add support for this VPN
> to RARE/freeRtr :-).
> 
> Cheers,
> -- 
> Simon.
> 
>> Tim
> 
>>> On 9 Feb 2022, at 15:55, mc36 <> wrote:
>>> 
>>> hi,
>>> 
>>> https://docs.google.com/document/d/1HbbLPnrFp_gbN-cVuOVXnV5B3VkZuRUBwn1n7kcM7GY/edit#
>>> 
>>> not a bad idea but imho this part is ready already
>>> 
>>> http://sources.nop.hu/misc/netconf/
>>> 
>>> is then current source of netconf files,
>>> but it's an automated tool to generate the yang files from the cli parser
>>> the same way we serve the ? output,
>>> the tab autocompletion
>>> and the junos set <somecommand>
>>> and maybe others...
>>> 
>>> the results are obviously not the ietf yang models but as i see, 
>>> basically nobody follows those... :)
>>> https://github.com/YangModels/yang/tree/master/vendor
>>> 
>>> regards,
>>> cs
>>> 
>