Re: [ipwave] IPWAVE Side Meeting
Alexandre Petrescu <alexandre.petrescu@gmail.com> Wed, 04 December 2019 11:04 UTC
Return-Path: <alexandre.petrescu@gmail.com>
X-Original-To: its@ietfa.amsl.com
Delivered-To: its@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 235CC120806 for <its@ietfa.amsl.com>; Wed, 4 Dec 2019 03:04:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.631
X-Spam-Level:
X-Spam-Status: No, score=-2.631 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_SOFTFAIL=0.665, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 MNnU-pKA-_3x for <its@ietfa.amsl.com>; Wed, 4 Dec 2019 03:04:23 -0800 (PST)
Received: from oxalide-smtp-out.extra.cea.fr (oxalide-smtp-out.extra.cea.fr [132.168.224.13]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CE4D51207FB for <its@ietf.org>; Wed, 4 Dec 2019 03:04:22 -0800 (PST)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by oxalide-sys.extra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id xB4B4JOx026115 for <its@ietf.org>; Wed, 4 Dec 2019 12:04:19 +0100
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 95073203FC4 for <its@ietf.org>; Wed, 4 Dec 2019 12:04:19 +0100 (CET)
Received: from muguet2-smtp-out.intra.cea.fr (muguet2-smtp-out.intra.cea.fr [132.166.192.13]) by pisaure.intra.cea.fr (Postfix) with ESMTP id 8B3D2203F65 for <its@ietf.org>; Wed, 4 Dec 2019 12:04:19 +0100 (CET)
Received: from [10.8.113.223] ([10.8.113.223]) by muguet2-sys.intra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id xB4B4IZq022348 for <its@ietf.org>; Wed, 4 Dec 2019 12:04:19 +0100
To: its@ietf.org
References: <CAPK2DeyAWKbA0jZmpSdvJVwG3RsqVd5c15r-wxTjEsH3uGbk0w@mail.gmail.com> <CAL1T1NEBoJUQWO1nWwoMwVEN6A+hsh4Qu09cGq0yeG-jkuWgeg@mail.gmail.com> <b14853b1-969a-9899-1201-2cb756fa6a07@gmail.com> <CAL1T1NEL+Z2em2+vFCQLXJJWKFg+snrX4MnPgn=WbjF6TEYegg@mail.gmail.com> <CAL1T1NEBrpkQfgoBN1mg0sJgQnpuMTzz+pZzhos=aM9vZOA6YA@mail.gmail.com> <9cddca74-4db3-1ea2-a10a-96b784e249ff@gmail.com>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <f8a4a1b3-3ebd-96bc-9878-ac0ea4682921@gmail.com>
Date: Wed, 04 Dec 2019 12:04:18 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.2.2
MIME-Version: 1.0
In-Reply-To: <9cddca74-4db3-1ea2-a10a-96b784e249ff@gmail.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: fr
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/its/shO9xAysdILifQgy0B8MgstuaKY>
Subject: Re: [ipwave] IPWAVE Side Meeting
X-BeenThere: its@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IPWAVE - IP Wireless Access in Vehicular Environments WG at IETF <its.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/its>, <mailto:its-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/its/>
List-Post: <mailto:its@ietf.org>
List-Help: <mailto:its-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/its>, <mailto:its-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 04 Dec 2019 11:04:26 -0000
I would like to make an additional remark, even though it might not be targeted to IPWAVE in particular, but more generally related to IPv6 experimentation in general. The 2001:db8:: addresses should not be used on computers, but on paper. In order to use something quickly on computers, I rather suggest addresses like 1::1 and 1::2. Other purists may suggest the ULA prefixes, like fd00::1 and fd00::2. But certainly not the 2001:db8::, which is called the 'Documentation Prefix' for a reason. Alex Le 04/12/2019 à 11:28, Alexandre Petrescu a écrit : > Hi Chris, > > Le 04/12/2019 à 06:23, Chris Shen a écrit : >> Hi Alex, >> >> Here I share wireshark packet dump file from the experiment of the >> hackathon. >> These packet information were collected during webcam streaming >> between two DSRC-enabled laptops. > > Thank you for the packet dumps. > > In the dumps I can see indeed UDP/IPv6 packets, supposedly for video > stream. > > However, I can not see the link layer headers, like 802.11 headers; I > only see EthernetII headers. The link layer headers can be captured in > monitor mode, not in normal mode. For that, there might be a need to > create a special interface (like wlan0 or so) with a command (maybe iw) > and capture on that interface, instead of capturing on the normal > interface. > >> If you have any questions, please let me know. >> >> BTW, when you setup your experiment platform, how did the IPv6 >> neighbor discovery work? >> Was it automatically running, or you need to manually configure it? > > ND worked fine. > > We do configure manually a few things for the initial connectivity: the > channels, the link-local addresses and some routing table entries. > > 'ND' has many parts: DAD, SLAAC, NS/NA, and others. > > I am not sure which part of ND you doubt it might not work. > > The part that I doubt very much is the following: when the card comes up > it must send an NA for its own address, to a multicast group; but has > this router, and the others, joined that group already? (MLD REPORT), or > probably not. If yes, then that initial NA has the right effect. If > not (the group is not yet formed), then the effect of that NA is lost - > another computer might form same LL address and DAD be nullified. > > In our settings, such a situation could be provoked: start a car remote > from this car, and then bring it closer. But we never faced it, because > we always start the cars at the same time and place. > > Another part of ND that might not work as appropriate is the use of RIO > in the RA. We rely on these RIOs to establish IP paths between cars. > These some times was failing in our initial tests, but we improved it, > with some pre-learned manually configured data, and other > pre-conditions. We wrote software to achieve that. > > SO, I am not sure which ND part you think about. > > What kind of ND proble do you foresee? > > Alex > >> >> >> Thanks! >> Chris. >> >> >> On Wed, Nov 27, 2019 at 6:41 PM Chris Shen <shenyiwen7@gmail.com >> <mailto:shenyiwen7@gmail.com>> wrote: >> >> Hi Alex, >> >> I answer your questions as follows: >> >> - is the manual available? ("Made a new manual for running OCB >> mode") >> >> Yes, it is in the following github link: >> >> https://github.com/ipwave-hackathon-ietf/ipwave-hackathon-ietf-106/blob/master/IPWAVE-Manual-Hackathon-IETF106-v0.2.pdf >> >> >> >> - have you made a patch file? >> >> I didn't make patch file for this implementation. >> Based on existing resources, there are some patch work to enable >> OCB mode in the Linux kernel. >> One of them is much concrete, which was made by Czech Technical >> University >> in Prague and Volkswagen. >> The resource link is as follows: >> https://ctu-iig.github.io/802.11p-linux/ >> But when I follow their instructions to configure OCB mode, there >> are some unclear steps and some compiling errors coming out, >> so I have modified the Makefile and explored other ways to configure >> OCB mode, which is shown in the manual. >> >> - did you use a notion of QoS? For example, can you send us a >> wireshark >> packet dump made in monitor mode, of the IPv6 packets used >> for video >> streaming between the two laptops? These packets have >> 802.11 QoS Data >> headers or just 802.11 Data headers? >> >> I didn't use QoS. For the current webcam streaming, I use gst-launch >> from Gstreamer. This gst-launch uses UDP and RTP to stream webcam. >> >> I checked packet dump, there is no QoS information, so I believe the >> packets >> just use 802.11 Data headers. >> I will send you the packet dump later, since I didn't save them. >> >> - the wifi card wilocity is on USB or is it internal to the >> laptop? >> >> For the current test, we replaced the original wifi card inside a >> laptop >> with an Athero wifi card using ath9k driver. This wifi card uses >> PCIe-mini >> interface to connect with the laptop. >> We also use the laptop internal antennas for 5.9GHz band. Initially, >> we are not sure if the antennas of the testing laptop can support >> 5.9GHz >> band, so we connect the wifi card with external antennas that >> support 5.9GHz. >> After testing, we found that the laptop internal antennas can also >> support >> 5.9GHz band, so we just use them. >> If you have a USB dongle that has PCIe-mini interface, I believe an >> Atheros wifi >> card can work as well, but you need to have external antennas to >> connect with >> the wifi card on the USB dongle. >> >> Thanks! >> Chris. >> >> >> On Tue, Nov 26, 2019 at 9:56 PM Alexandre Petrescu >> <alexandre.petrescu@gmail.com <mailto:alexandre.petrescu@gmail.com>> >> wrote: >> >> Hi Chris, >> >> With respect to the Hackathon slides, my colleague and I would >> like to >> ask you: >> >> - is the manual available? ("Made a new manual for running OCB >> mode") >> - have you made a patch file? >> - did you use a notion of QoS? For example, can you send us a >> wireshark >> packet dump made in monitor mode, of the IPv6 packets used >> for video >> streaming between the two laptops? These packets have >> 802.11 QoS Data >> headers or just 802.11 Data headers? >> - the wifi card wilocity is on USB or is it internal to the >> laptop? >> >> Yours, >> >> Alex >> >> Le 21/11/2019 à 08:13, Chris Shen a écrit : >> > Hi its, >> > >> > Here I share side meeting slides for IPWAVE WG. >> > >> > Please join us to give your opinions and suggestions about >> the work in >> > IPWAVE WG. >> > >> > We really need your input! ^_^ >> > >> > Thanks! >> > Chris. >> > >> > >> > >> > On Thu, Nov 21, 2019 at 11:12 AM Mr. Jaehoon Paul Jeong >> > <jaehoon.paul@gmail.com <mailto:jaehoon.paul@gmail.com> >> <mailto:jaehoon.paul@gmail.com <mailto:jaehoon.paul@gmail.com>>> >> wrote: >> > >> > Hi IPWAVE WG, >> > >> > There will be a side meeting for I2NSF WG's next steps >> from 3:30PM >> > to 4:30PM today >> > at Bras Basah. >> > >> >> https://datatracker.ietf..org/meeting/106/floor-plan?room=bras-basah#raffles-city-convention-center >> >> > >> <https://datatracker.ietf.org/meeting/106/floor-plan?room=bras-basah#raffles-city-convention-center> >> >> > >> > >> > The agenda for IPWAVE side meeting is as follows: >> > >> > - IPWAVE Hackathon Project (Yiwen Chris Shen, 5 min) >> > - IPWAVE Problem Statement Draft (Jaehoon Paul Jeong, 5 >> min) >> > - Vehicular Neighbor Discovery Draft (Yiwen Chris Shen, 5 >> min) >> > - Vehicular Mobility Management Draft (Yiwen Chris Shen, >> 5 min) >> > - Security and Privacy Draft (Jaehoon Paul Jeong, 5 min) >> > - Context-Aware Navigator Draft (Yiwen Chris Shen, 5 min) >> > - Open Discussion for IPWAVE WG Progress (30 min) >> > >> > The main purpose of this side meeting is to share the >> progress of >> > IPWAVE PS draft and the IPWAVE hackathon project using >> the video >> > delivery in the Linux system for IPv6 over IEEE >> 802.11-OCB. >> > >> > I would like to explain the status of our WG and the >> importance of >> > the IPWAVE PS draft for the next step of our WG. >> > >> > Welcome your engagement and feedback. >> > >> > Thanks. >> > >> > Best Regards, >> > Paul >> > >> > -- >> > You received this message because you are subscribed to >> the Google >> > Groups "skku-iotlab-members" group. >> > To unsubscribe from this group and stop receiving emails >> from it, >> > send an email to >> skku-iotlab-members+unsubscribe@googlegroups.com >> <mailto:skku-iotlab-members%2Bunsubscribe@googlegroups.com> >> > <mailto:skku-iotlab-members+unsubscribe@googlegroups.com >> <mailto:skku-iotlab-members%2Bunsubscribe@googlegroups.com>>. >> > To post to this group, send email to >> > skku-iotlab-members@googlegroups.com >> <mailto:skku-iotlab-members@googlegroups.com> >> > <mailto:skku-iotlab-members@googlegroups.com >> <mailto:skku-iotlab-members@googlegroups.com>>. >> > To view this discussion on the web visit >> > >> >> https://groups.google.com/d/msgid/skku-iotlab-members/CAPK2DeyAWKbA0jZmpSdvJVwG3RsqVd5c15r-wxTjEsH3uGbk0w%40mail.gmail.com >> >> > >> <https://groups.google.com/d/msgid/skku-iotlab-members/CAPK2DeyAWKbA0jZmpSdvJVwG3RsqVd5c15r-wxTjEsH3uGbk0w%40mail.gmail.com?utm_medium=email&utm_source=footer>. >> >> > For more options, visit >> https://groups.google.com/d/optout. >> > >> > >> > >> > -- >> > Yiwen (Chris) Shen, Ph.D. Candidate >> > >> > Homepage: https://chrisshen.github.io >> > IoT Lab: _http://iotlab.skku.edu <http://iotlab.skku.edu/>_ >> > Sungkyunkwan University, Suwon, South Korea >> > Mobile:+82-(0)10-6871-8103 >> > Email: chrisshen@skku.edu <mailto:chrisshen@skku.edu> >> > <mailto:chrisshen@skku.edu <mailto:chrisshen@skku.edu>> >> > >> > _______________________________________________ >> > its mailing list >> > its@ietf.org <mailto:its@ietf.org> >> > https://www.ietf.org/mailman/listinfo/its >> > >> >> >> >> -- Yiwen (Chris) Shen, Ph.D. Candidate >> >> Homepage: https://chrisshen.github.io >> IoT Lab: _http://iotlab.skku.edu <http://iotlab.skku.edu/>_ >> Sungkyunkwan University, Suwon, South Korea >> Mobile:+82-(0)10-6871-8103 >> Email: chrisshen@skku.edu >> <mailto:chrisshen@skku.edu> >> >> >> >> -- >> Yiwen (Chris) Shen, Ph.D. Candidate >> >> Homepage: https://chrisshen.github.io >> IoT Lab: _http://iotlab.skku.edu <http://iotlab.skku.edu/>_ >> Sungkyunkwan University, Suwon, South Korea >> Mobile:+82-(0)10-6871-8103 >> Email: chrisshen@skku.edu >> <mailto:chrisshen@skku.edu> > > _______________________________________________ > its mailing list > its@ietf.org > https://www.ietf.org/mailman/listinfo/its
- [ipwave] IPWAVE Side Meeting Mr. Jaehoon Paul Jeong
- Re: [ipwave] IPWAVE Side Meeting Chris Shen
- Re: [ipwave] IPWAVE Side Meeting Alexandre Petrescu
- Re: [ipwave] IPWAVE Side Meeting Chris Shen
- Re: [ipwave] IPWAVE Side Meeting Chris Shen
- Re: [ipwave] IPWAVE Side Meeting Alexandre Petrescu
- Re: [ipwave] IPWAVE Side Meeting Alexandre Petrescu
- Re: [ipwave] IPWAVE Side Meeting Chris Shen
- Re: [ipwave] IPWAVE Side Meeting Alexandre Petrescu
- Re: [ipwave] IPWAVE Side Meeting Alexandre Petrescu