Re: [v6ops] Eating our own dog food : students solving IPv6 entreprise multihoming

Jeff Tantsura <jefftant.ietf@gmail.com> Thu, 20 July 2017 07:15 UTC

Return-Path: <jefftant.ietf@gmail.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 73557131CE4; Thu, 20 Jul 2017 00:15:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-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 P1PuEbF9zkNK; Thu, 20 Jul 2017 00:15:25 -0700 (PDT)
Received: from mail-wr0-x236.google.com (mail-wr0-x236.google.com [IPv6:2a00:1450:400c:c0c::236]) (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 1B73B12EB2B; Thu, 20 Jul 2017 00:15:25 -0700 (PDT)
Received: by mail-wr0-x236.google.com with SMTP id k71so13378633wrc.2; Thu, 20 Jul 2017 00:15:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=user-agent:date:subject:from:to:message-id:thread-topic:references :in-reply-to:mime-version:content-transfer-encoding; bh=xBdyydK8L2NOQp5Jo0SIxG8n9Vw/b4ht3+eCVvNgAd4=; b=tY/2N6QEKSOIE5SDI2dz4rpqoK7y6/kmFczkYP0Q3xy2rgi9Stz0DXQvD4KNNwrhzJ vzMNxBvM1C1og74s0i2fej2asUQHKiue0TMI408NB9OajkMYiFqvowNa9ny+PKRXgrmB k2a4NHLl0//YfJmhsAzGx9Qt7cTmGF0KU8/Vby7Xsvg2W7JcgOLGNAJBgP3aiB98nHfv mmhNWQLC1HtL2O32E67Yz/Q+quNZeDRFsvkCKQnkqAAkN62rNTBb6QDDr71UUkyaDk1G NKwBfDWmMU8s6iUfMz7FuZqvJ4utWj4H9vqzrG109SLe1zR3z1z0MmLShliohWICmhAo 3EfA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:user-agent:date:subject:from:to:message-id :thread-topic:references:in-reply-to:mime-version :content-transfer-encoding; bh=xBdyydK8L2NOQp5Jo0SIxG8n9Vw/b4ht3+eCVvNgAd4=; b=eTdHWh179f24G5QLrHTaQ+d2hHba1VzlRSvXGEatLwZwV0jY7Ku0ikRNvBESuSYOIX xayG02migD7EYRiBw2ysTI/lBZ/JeDarn1D0C/bItlzs1w6Lnbh1WJuTNHNY1TgGjLsp bfO7aShEcTrNuN8GTEqcz2TGJDpEzSkBWNOZ+L4l5D7k3dHH+sHzMuMpKFyZTRTGmM4u nqGC4tbw2IQzDHLQtlKMNarm42MzL3bIEBrrwE9jf1WQwJHwX2ac22Fynw2QunbTzUSw wZDDvdIha3Shok4XgTijzYkq7CuVp8F6OJDvIt4z1eRDAebFDwSRtBxlKLTGuPQxKdwj wxTw==
X-Gm-Message-State: AIVw111c8gY+p7lH1bkelc05wx7Qrczw3vfa7+7K3o7+RD+1doefQops nhp3YL3DD2hxIA==
X-Received: by 10.223.168.110 with SMTP id l101mr2078535wrc.251.1500534923594; Thu, 20 Jul 2017 00:15:23 -0700 (PDT)
Received: from [10.0.3.168] ([62.168.35.125]) by smtp.gmail.com with ESMTPSA id r199sm1287238wmd.11.2017.07.20.00.13.26 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 20 Jul 2017 00:15:22 -0700 (PDT)
User-Agent: Microsoft-MacOutlook/f.24.0.170702
Date: Thu, 20 Jul 2017 09:12:18 +0200
From: Jeff Tantsura <jefftant.ietf@gmail.com>
To: Olivier Bonaventure <olivier.bonaventure@tessares.net>, RTGWG <rtgwg@ietf.org>, V6 Ops List <v6ops@ietf.org>
Message-ID: <6C482CA8-5E8A-47B6-A76E-D3A47B7F70B3@gmail.com>
Thread-Topic: Eating our own dog food : students solving IPv6 entreprise multihoming
References: <a174658e-edab-bda6-f6b8-24014ea57d6b@tessares.net>
In-Reply-To: <a174658e-edab-bda6-f6b8-24014ea57d6b@tessares.net>
Mime-version: 1.0
Content-type: text/plain; charset="UTF-8"
Content-transfer-encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/gdCOUwVQYUsKHPZZGKF-DR9qhYw>
Subject: Re: [v6ops] Eating our own dog food : students solving IPv6 entreprise multihoming
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Jul 2017 07:15:27 -0000

Olivier,

Thank you for sharing with RTGWG and looking forward to your future contributions!

Cheers,
Jeff
-----Original Message-----
From: rtgwg <rtgwg-bounces@ietf.org> on behalf of Olivier Bonaventure <olivier.bonaventure@tessares.net>
Date: Thursday, July 20, 2017 at 08:54
To: RTGWG <rtgwg@ietf.org>, V6 Ops List <v6ops@ietf.org>
Subject: Eating our own dog food : students solving IPv6 entreprise multihoming

    Hello,
    
    During v6ops and yesterday's plenary, John Brzozowski encouraged us to 
    use our own technologies for the IETF network with NAT64. This argument 
    is valid for those who teach computer networks and since RTGWG is 
    working on enterprise IPv6 multihoming, you might be interested in a 
    recent experiment we did with our students.
    
    When students learn networking, they should not learn the current state 
    of affairs but be prepared for the future since they'll only graduate in 
    a few years. Several years ago, when IPv6 deployment was burgeoning, I 
    decided to remove IPv4 from my networking 101 open-source textbook
    ( http://cnp3book.info.ucl.ac.be ). Since then, our students only learn 
    IPv6 and results are excellent. Once they've learned IPv6, they can 
    quickly understand how IPv4 works. Hopefully they'll see sunset4 during 
    their career.
    
    After networking 101, some of your students attend an advanced 
    networking course. This course combines theory with practice and usually 
    students do practice after theory to illustrate the theoratical 
    concepts. This year, we decided to flip the course and start from a 
    practical problem to see how groups of students can address this problem 
    with an open mindset and based only on what they've learned from 
    networking 101 and the information that they will find on the Internet. 
    During their carreer, they will be forced to learn on the spot anyway 
    and they should better start early to look at rfcs, internet drafts and 
    open-source implementations.
    
    The project given to the students was very simple. One of the engineers 
    responsible for our (IPv4 mainly :-() campus network explained the 
    architecture and the basic openrational principles that they use. 
    Olivier Tilmans prepared a virtual machine that mimics our compus 
    network (basically six routers) and we attached a few virtual machines 
    to act as servers and clients. The only constraint that we was that the 
    campus network had two upstream providers each delegating a different 
    prefix to the campus network.
    
    Then, the students had to  :
    - define an IPv6 addressing plan for their network
    - select, install and configure a routing protocol and make sure that it 
      was working correctly
    - install and configure dhcp servers/ra to distribute addresses
    - install and configure DNS servers and resolvers
    - install and configure Diffserv-like traffic control
    - install and configure ssh and http servers
    - install and configure firewall services to protect the network
    - think about a solution to monitor the network
    
    [the number of tasks was chosen based on the number of students in each 
    group]
    
    All student teams had an operation network at the end of the project. 
    Since we believe in automation and open-source, we required them to 
    automate their network from day one and several groups have released 
    their entire project in open-source.
    
     From a teaching viewpoint, entreprise IPv6 multihoming is a very nice 
    problem. To encourage other educators (and maybe also network engineers 
    willing to continue to learn) to experiment with IPv6 entreprise 
    multihoming, we have released all the software developed to create this 
    project in open-source.
    
    You can find all the details at :
    
    https://github.com/UCL-INGI/lingi2142
    
    You only need a Linux virtual machine provided by Vagrant to reproduce 
    the experiment. The barrier to experiment with IPv6 entreprise 
    multihoming is very low.
    
    Selected students projects with reports and code are available from this 
    repository as well
    
    https://github.com/UCL-INGI/lingi2142/tree/master/student_projects
    
    I encourage you to have a look at the students' reports to see their 
    final results:
    https://github.com/UCL-INGI/lingi2142/blob/master/student_projects/Group1/report-group1.pdf
    https://github.com/UCL-INGI/lingi2142/blob/master/student_projects/Group2/LINGI2142___Rapport_Groupe_2.pdf
    https://github.com/UCL-INGI/lingi2142/blob/master/student_projects/Group3/report.pdf
    
    Comments and feedback are welcome although the IETF mailing lists may 
    not be the best place for discussions on software or teaching projects...
    
    
    Olivier Tilmans and Olivier Bonaventure
    
    
    -- 
    
    ------------------------------
    DISCLAIMER.
    This email and any files transmitted with it are confidential and intended 
    solely for the use of the individual or entity to whom they are addressed. 
    If you have received this email in error please notify the system manager. 
    This message contains confidential information and is intended only for the 
    individual named. If you are not the named addressee you should not 
    disseminate, distribute or copy this e-mail. Please notify the sender 
    immediately by e-mail if you have received this e-mail by mistake and 
    delete this e-mail from your system. If you are not the intended recipient 
    you are notified that disclosing, copying, distributing or taking any 
    action in reliance on the contents of this information is strictly 
    prohibited.
    
    _______________________________________________
    rtgwg mailing list
    rtgwg@ietf.org
    https://www.ietf.org/mailman/listinfo/rtgwg