Re: [Emo-dir] [edu-team] Educational RFCs

ehalep@gmail.com Thu, 14 April 2022 14:49 UTC

Return-Path: <ehalep@gmail.com>
X-Original-To: emo-dir@ietfa.amsl.com
Delivered-To: emo-dir@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 089DE3A1BAE for <emo-dir@ietfa.amsl.com>; Thu, 14 Apr 2022 07:49:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.107
X-Spam-Level:
X-Spam-Status: No, score=-2.107 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, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 EbU-1XKECQZt for <emo-dir@ietfa.amsl.com>; Thu, 14 Apr 2022 07:49:27 -0700 (PDT)
Received: from mail-ed1-x52b.google.com (mail-ed1-x52b.google.com [IPv6:2a00:1450:4864:20::52b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 907C03A1BAD for <emo-dir@ietf.org>; Thu, 14 Apr 2022 07:49:26 -0700 (PDT)
Received: by mail-ed1-x52b.google.com with SMTP id g20so6666497edw.6 for <emo-dir@ietf.org>; Thu, 14 Apr 2022 07:49:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=from:to:cc:references:in-reply-to:subject:date:message-id :mime-version:content-transfer-encoding:thread-index :content-language; bh=nEjMdOHbofsZ8lZFsyGRbfc24E7tsSUfdElR7eDTqE8=; b=WnpfozYKlcjAWuNe0DfpHLse5izeuKYWMRKwwu57FIb5tdRD4f4P2sYGyElof4/WfL 6YBIz/xJsRrJq5OIrMwP2y2ifc/Eq7AxlGEc7jjTihQ2vgc3hMyB7lXj1SSe5wI5z9yr 38mTmpaertEv1SVmqLxjPeuMu83zWMbtf4ZyZwkohGZaVy0eY0voWBxnkWrgcWfi2i7M NGjeBfgObHFfNSqYaO6CAajI4T+z2nIZSzVkihet/LUCmWFD6EYi/7T+U/dafh10WZ63 sAVzZeqTpp/va4TriFSA7IMkibHfcwnd1fisVrlmGWE71/bLB7hAPTcSo6pa8WvrrQ6K /wNg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:from:to:cc:references:in-reply-to:subject:date :message-id:mime-version:content-transfer-encoding:thread-index :content-language; bh=nEjMdOHbofsZ8lZFsyGRbfc24E7tsSUfdElR7eDTqE8=; b=rhwgSmaqhcgy1ASe1xVdxTFzzzpkZ0KYzETiJGmNkaHySnAOUGpl18G7+seo7YvYwi ccEJocdqx6sojxniglUKb4H2WgQaPf+RCIqFyJt+sE/KtnysQIjCUyt+g+F6Yi+zDxeN DMcZ0ULB0DIJM0/zKOAFaezg+i5sflWixfgJzfGZIbvhNeAjNRsps5ncXfkeya27R9n4 nWyisR+z3eGAN9ckCR9nrF7EIdtHmTBCKn6kgcDoWizmhFkt8ICFeZMDgCKN872h5Ug9 hsIkLUDifz3pBFPzmiI7GXWH88Aw7dfgpgQfyJW/XBtDUaHudMToRga1t39pjL0uV7Kt c3nQ==
X-Gm-Message-State: AOAM530H5aqwt1US1YFUBYLOdIyofjsLSFvqAVtaAzjXdBwn0dibRbjG W053kCnqW6mpvpBNrvfu/pScV4Uyoz4=
X-Google-Smtp-Source: ABdhPJzQPZrHIDg55IF+uK2wn9nw8fwXNcoiiuCB4X0ib7Cjy1RufRBzDBbTM+9+ryZoqVbpB3/qGQ==
X-Received: by 2002:a05:6402:5245:b0:419:5437:fc6b with SMTP id t5-20020a056402524500b004195437fc6bmr3404883edd.282.1649947764718; Thu, 14 Apr 2022 07:49:24 -0700 (PDT)
Received: from DESKTOPEHAL (ppp079166012198.access.hol.gr. [79.166.12.198]) by smtp.gmail.com with ESMTPSA id d1-20020a170906174100b006e85e9903f2sm703869eje.89.2022.04.14.07.49.23 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Thu, 14 Apr 2022 07:49:24 -0700 (PDT)
From: ehalep@gmail.com
To: 'Greg Wood' <ghwood@staff.ietf.org>
Cc: "'Salz, Rich'" <rsalz@akamai.com>, emo-dir@ietf.org, arouskas@unipi.gr
References: <006f01d7677c$13b31cb0$3b195610$@gmail.com> <B15E0308-81BF-4558-B2FC-0E9DDF77CA8C@akamai.com> <03d801d84df1$8737fc80$95a7f580$@gmail.com> <5093837D-22C6-4FF6-BA65-8AE3063B7ECB@staff.ietf.org>
In-Reply-To: <5093837D-22C6-4FF6-BA65-8AE3063B7ECB@staff.ietf.org>
Date: Thu, 14 Apr 2022 17:49:21 +0300
Message-ID: <019101d8500e$d43818c0$7ca84a40$@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQMP5jKy9QpVT65xqR2xuIiHQXY16gGn8LfrAiavSg0CIjRRp6pNuG1Q
Content-Language: el
Archived-At: <https://mailarchive.ietf.org/arch/msg/emo-dir/nZj3XZZj7EIhYpX9xZkIDWlxKcI>
Subject: Re: [Emo-dir] [edu-team] Educational RFCs
X-BeenThere: emo-dir@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Education, Mentoring & Outreach Directorate" <emo-dir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/emo-dir>, <mailto:emo-dir-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/emo-dir/>
List-Post: <mailto:emo-dir@ietf.org>
List-Help: <mailto:emo-dir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/emo-dir>, <mailto:emo-dir-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Apr 2022 14:49:32 -0000

Greetings Greg,

Thanks for your email, and I also would like to thank Rich for reviving this thread (I should have done that in the previous email!).

Thank you for your pointers, while we were aware of xml2rfc and other tools for authoring IETF documents, we were not aware of those resources being brought together. We are thinking of how to incorporate these tools in our course.

As per our initial email, our initial goal in this venture is to familiarize our students with the IETF format and make them able to read, understand and implement a small networking protocol. Keep in mind that our target audience, for that specific course, are undergraduate students.

So, we were discussing the possibility of co-creating a couple of very basic introductory IETF documents, published by the edu-team, with the sole purpose of providing outreach educational material to interested academic institutions that would like to train their students in reading, implementing, and understanding the IETF RFC series. While this is the second year we have integrated this work in our curriculum, it would be more beneficial for us and our students to have simple and basic IETF RFCs that they can work on.

We do understand that the role of the edu-team of the IETF is to provide materials for the attendees, however we're asking to see whether it may be of interest to the community to increase the scope of the charter to provide educational material outside of the IETF members. We would be very interested in collaborating in such a context with both writing documents as well as using these into our course.

Regards,
Evangelos.

-----Original Message-----
From: Greg Wood <ghwood@staff.ietf.org> 
Sent: Τρίτη, 12 Απριλίου 2022 17:58
To: ehalep@gmail.com
Cc: Salz, Rich <rsalz@akamai.com>; emo-dir@ietf.org; arouskas@unipi.gr
Subject: Re: [Emo-dir] [edu-team] Educational RFCs

Hello!

With many thanks to Rich for picking this up and to you for the reply, you and your students might find a few new-since-last-year resources interesting:

https://authors.ietf.org

and

https://author-tools.ietf.org

also, this webpage:

https://www.ietf.org/standards/rfcs/

was recently revised, including a link to this blog post, which might be useful:

https://www.ietf.org/blog/how-read-rfc/

In any case, I would be very interested in talking about this further.

Regards,

-Greg

> On 11, Apr2022, at 18:14, <ehalep@gmail.com> <ehalep@gmail.com> wrote:
> 
> Greetings,
> 
> Certainly, we are still working on this.
> Last year, it went very well, and our students were very interested in this exercise and got a real handle on being able to read a very simple protocol, written with the IETF format and of course using the necessary tools (xml2rfc + ipnits, etc.). We got some pretty good results.
> 
> We are going to make the same exercise this year as well, so yes, we are interested in this work.
> 
> Regards,
> Evangelos Haleplidis.
> 
> From: Salz, Rich <rsalz@akamai.com>
> Sent: Τρίτη, 12 Απριλίου 2022 00:00
> To: ehalep@gmail.com; emo-dir@ietf.org
> Cc: arouskas@unipi.gr
> Subject: Re: [edu-team] Educational RFCs
> 
> Hi there.  Resurrecting this.  Sorry for the nearly-a-year without any reply (that I saw).  Are you still interested in talking about this?
> 
> From: "ehalep@gmail.com" <ehalep@gmail.com>
> Date: Tuesday, June 22, 2021 at 11:34 AM
> To: "edu-team@ietf.org" <edu-team@ietf.org>
> Cc: "arouskas@unipi.gr" <arouskas@unipi.gr>
> Subject: [edu-team] Educational RFCs
> 
> Greetings to the edu-team,
> 
> Apologies if this has already been discussed in the past. I searched the mail archives as much as possible but couldn’t find anything similar.
> 
> On a course on Internet Protocols at the University of Piraeus (https://www.ds.unipi.gr/en/courses/internet-protocols-2/), Professor Rouskas and I, have begun a series of laboratory exercises where we want our students to become adept at being able to read and implement internet protocol specification documents, specifically from the IETF.
> 
> With that goal in mind, we wrote a small IETF-like draft (using xml2rfc) where we outlined a very simple protocol in detail and asked them to read and implement it.
> 
> That got us thinking whether it makes sense for the IETF and specifically for the edu-team to create a series of educational RFCs with the goal of providing material for Universities for preparing students/future-engineers to be ready to participate in the IETF.
> 
> We do understand that this is not the current focus of the edu-team and the IETF in particular, but we were thinking whether it makes sense to expand the charter to allow creating short introductory RFCs, where attendees/students could be introduced into reading and understanding specs at a smaller scale.
> 
> Regards,
> Evangelos Haleplidis.
> _______________________________________________
> Emo-dir mailing list
> Emo-dir@ietf.org
> https://www.ietf.org/mailman/listinfo/emo-dir