From nobody Mon Sep 7 07:58:32 2020 Return-Path: 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 C93F93A0F71 for ; Mon, 7 Sep 2020 07:58:30 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 3.431 X-Spam-Level: *** X-Spam-Status: No, score=3.431 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, DKIM_ADSP_CUSTOM_MED=0.001, FORGED_GMAIL_RCVD=1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, NML_ADSP_CUSTOM_MED=0.9, SPF_HELO_NONE=0.001, SPF_SOFTFAIL=0.665, SPOOFED_FREEMAIL=1.361, URIBL_BLOCKED=0.001] autolearn=no 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 t-12xo_uDlsq for ; Mon, 7 Sep 2020 07:58:29 -0700 (PDT) Received: from smtp4-g21.free.fr (smtp4-g21.free.fr [IPv6:2a01:e0c:1:1599::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 40AF53A0F13 for ; Mon, 7 Sep 2020 07:58:29 -0700 (PDT) Received: from [IPv6:2a01:e35:2e59:ce10::da3d:a356] (unknown [IPv6:2a01:e35:2e59:ce10::da3d:a356]) by smtp4-g21.free.fr (Postfix) with ESMTP id EEBF119F58C for ; Mon, 7 Sep 2020 16:58:26 +0200 (CEST) To: IPWAVE WG From: Alexandre Petrescu Message-ID: <95aff146-f04a-dc9f-93fd-1175d1a0bfcb@gmail.com> Date: Mon, 7 Sep 2020 16:58:26 +0200 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.12.0 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="------------C75893D8CCB4F3EFFAA7BB05" Content-Language: fr Archived-At: Subject: [ipwave] Requirement of IPv6 access for ITS Code Hub 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Sep 2020 14:58:31 -0000 This is a multi-part message in MIME format. --------------C75893D8CCB4F3EFFAA7BB05 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: quoted-printable Hi, I think it might be possible to formulate a requirement to access the=20 ITS Code Hub on IPv6. https://its.dot.gov/code/ Currently, the above URL is not reachable on IPv6. It is an ITS URL and all ITS specifications are based on IPv6, not on IPv= 4. It is a DoT URL and I DoT promotes IPv6. It is a .gov URL and I think also the .gov promotes IPv6. Surprisingly though, the above URL does not use IPv6. I must say that in the country where I live the gouv.fr also promotes=20 IPv6 to a certain extent even though few if any of its URLs are on=20 IPv6.=C2=A0 But, at the same time I could spot a few Internet organisatio= ns=20 in several countries whose URLs do work on IPv6. (RIPE, UKNOF, NANOG,=20 potentially others). Alex --------------C75893D8CCB4F3EFFAA7BB05 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 8bit

Hi,

I think it might be possible to formulate a requirement to access the ITS Code Hub on IPv6.

https://its.dot.gov/code/

Currently, the above URL is not reachable on IPv6.

It is an ITS URL and all ITS specifications are based on IPv6, not on IPv4.

It is a DoT URL and I DoT promotes IPv6.

It is a .gov URL and I think also the .gov promotes IPv6.

Surprisingly though, the above URL does not use IPv6.

I must say that in the country where I live the gouv.fr also promotes IPv6 to a certain extent even though few if any of its URLs are on IPv6.  But, at the same time I could spot a few Internet organisations in several countries whose URLs do work on IPv6. (RIPE, UKNOF, NANOG, potentially others).

Alex

--------------C75893D8CCB4F3EFFAA7BB05-- From nobody Wed Sep 9 05:49:13 2020 Return-Path: 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 925133A0AA6 for ; Wed, 9 Sep 2020 05:49:11 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 3.931 X-Spam-Level: *** X-Spam-Status: No, score=3.931 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, DKIM_ADSP_CUSTOM_MED=0.001, FORGED_GMAIL_RCVD=1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_SOFTFAIL=0.665, SPOOFED_FREEMAIL=1.361] autolearn=no 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 k3mkUOG4EjFf for ; Wed, 9 Sep 2020 05:49:10 -0700 (PDT) Received: from cirse-smtp-out.extra.cea.fr (cirse-smtp-out.extra.cea.fr [132.167.192.148]) (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 507723A0AA3 for ; Wed, 9 Sep 2020 05:49:10 -0700 (PDT) Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by cirse-sys.extra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id 089Cn8j3010231 for ; Wed, 9 Sep 2020 14:49:08 +0200 Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id B7B0720510E for ; Wed, 9 Sep 2020 14:49:08 +0200 (CEST) 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 ABE73205172 for ; Wed, 9 Sep 2020 14:49:08 +0200 (CEST) Received: from [10.8.35.150] (is154594.intra.cea.fr [10.8.35.150]) by muguet2-sys.intra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id 089Cn8Xi029387 for ; Wed, 9 Sep 2020 14:49:08 +0200 To: IPWAVE WG From: Alexandre Petrescu Message-ID: Date: Wed, 9 Sep 2020 14:49:09 +0200 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.12.0 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="------------8EA3E90AFC8646B32DAA32A3" Content-Language: fr Archived-At: Subject: [ipwave] 802.11bd D1.0 preliminary spec available somewhere? 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Sep 2020 12:49:12 -0000 This is a multi-part message in MIME format. --------------8EA3E90AFC8646B32DAA32A3 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Hi, I am looking for the IEEE 802.11bd D1.0 preliminary spec.  Is it available somewhere I could look at it? It is to see whether, hopefully, it cites RFC8691 for IPv6 use. Alex --------------8EA3E90AFC8646B32DAA32A3 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 8bit

Hi,

I am looking for the IEEE 802.11bd D1.0 preliminary spec.  Is it available somewhere I could look at it?

It is to see whether, hopefully, it cites RFC8691 for IPv6 use.

Alex

--------------8EA3E90AFC8646B32DAA32A3-- From nobody Wed Sep 9 14:41:39 2020 Return-Path: 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 A3C653A0EF1 for ; Wed, 9 Sep 2020 14:41:37 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.898 X-Spam-Level: X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=us-toyota-itc-com.20150623.gappssmtp.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 eBlzq0Uqnucj for ; Wed, 9 Sep 2020 14:41:36 -0700 (PDT) Received: from mail-yb1-xb29.google.com (mail-yb1-xb29.google.com [IPv6:2607:f8b0:4864:20::b29]) (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 0B0413A0EEE for ; Wed, 9 Sep 2020 14:41:35 -0700 (PDT) Received: by mail-yb1-xb29.google.com with SMTP id u6so2761129ybf.1 for ; Wed, 09 Sep 2020 14:41:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=us-toyota-itc-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=S11hnoFcLBmdEW0CLQKMTRJFY6LyJ298B2KtRcN8eds=; b=peNGKDUxu0KFKcczRnbL+SbcOYwLVJSYmTx+AenZXIhChTCkW3Hs4Qll5GvAlASF2K Mfcouv+dYwJay3o/TTHcS6F+C8a2dvIxQMdMIP1kQrXlCv3BffdBBOcmg/MQnbeJXVWp st3jNwBKtqn+Wpl882KWE4Wtlv0jYtf+R+/E12oBCKM97DBXSqzqqFxOYCFXAI1jZozX 5j5DoCv/9MJWQ1uojHiUGeybCQyQwbhwlTV/YqJA6Y+eGqZ+fYnhoTYriefv3ihEA9ao 80Uu2o7gb07m3zUoJQYfQlDIukdBPfi7nr3YB/NK6nVbTxo0ywX0OuLus5DKp1BrcIWs yhWg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=S11hnoFcLBmdEW0CLQKMTRJFY6LyJ298B2KtRcN8eds=; b=TXYErZad4Gy8GX7URhkFpV5o9bMB9XM1mSJu8oYDKO8l+Ah95bp2pWmqG0/G3dRv8H TGdtBrMHnRHLSOTbZ40p8zEbrCoY00K+6uC3QAZeJ0I9HoXSQ4ixzByGpzirO8KtiKPR BnOS5NGhxjjv0yqaC8S00+GMfe9WrYCQ9r4x1GoobNYE2cCFBWWyEX0MQOww4PA5NgSc 06u0inSebFeHolYpK5kjhBJMKVDsQp7HfWcdrtWeFtYEhUs9w/KdTCUAaG8aHGgJ7SzU uRcpjMy5RTF7dhbKXt10HVmZKYONbS0aVE6o8cWj9znjgH2m805uIq5l/mF7xTP8NR9l sgqA== X-Gm-Message-State: AOAM532iUACERAzBYptuBLMxkUJYa5qfuwGfvVjJmfJLez9d2XOvERdE dofffIet01PBi2TEQ05gVQn/hxTFcDPEYBfZKa/i2w== X-Google-Smtp-Source: ABdhPJxw5vY74RjtzJAm3l4PuUTVuU/IPUz9SZcFyHA9LWvmrqtjqWvcgDMzXk+Sj2GFgJQIMcBkraywaW0mRu30RXI= X-Received: by 2002:a25:9c44:: with SMTP id x4mr8220748ybo.28.1599687694781; Wed, 09 Sep 2020 14:41:34 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: John Kenney Date: Wed, 9 Sep 2020 14:41:30 -0700 Message-ID: To: Alexandre Petrescu Cc: IPWAVE WG Content-Type: multipart/alternative; boundary="000000000000cca87c05aee850a5" Archived-At: Subject: Re: [ipwave] 802.11bd D1.0 preliminary spec available somewhere? 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Sep 2020 21:41:38 -0000 --000000000000cca87c05aee850a5 Content-Type: text/plain; charset="UTF-8" Hi Alex, No, this is a work in progress, scheduled to be completed later this month. It will be a draft standard. Unless a decision is made to make it available for sale, it will only be available to IEEE 802.11 WG voting members. Best Regards, John On Wed, Sep 9, 2020 at 5:49 AM Alexandre Petrescu < alexandre.petrescu@gmail.com> wrote: > Hi, > > I am looking for the IEEE 802.11bd D1.0 preliminary spec. Is it available > somewhere I could look at it? > > It is to see whether, hopefully, it cites RFC8691 for IPv6 use. > > Alex > _______________________________________________ > its mailing list > its@ietf.org > https://www.ietf.org/mailman/listinfo/its > -- John Kenney Director and Sr. Principal Researcher Toyota InfoTech Labs 465 Bernardo Avenue Mountain View, CA 94043 Tel: 650-694-4160. Mobile: 650-224-6644 --000000000000cca87c05aee850a5 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi Alex,

No, this is a work in progress= , scheduled to be completed later this month. It will be a draft standard. = Unless a decision is made to make it available for sale, it will only be av= ailable to IEEE 802.11 WG voting members.

Best Reg= ards,
John


On Wed, Sep 9, 2020 at 5:49 AM Ale= xandre Petrescu <alexand= re.petrescu@gmail.com> wrote:
=20 =20 =20

Hi,

I am looking for the IEEE 802.11bd D1.0 preliminary spec.=C2=A0 Is it available somewhere I could look at it?

It is to see whether, hopefully, it cites RFC8691 for IPv6 use.

Alex

_______________________________________________
its mailing list
its@ietf.org
https://www.ietf.org/mailman/listinfo/its


--
John Kenney
Director and Sr. Principal Researcher
Toyota InfoTech Labs
465 Bernardo Avenue
Mountain View, CA 94043
Tel: 650-694-4160. Mobile: 650-224-6644
<= /div>
--000000000000cca87c05aee850a5-- From nobody Thu Sep 10 00:08:03 2020 Return-Path: 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 7216E3A104C for ; Thu, 10 Sep 2020 00:08:01 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.277 X-Spam-Level: X-Spam-Status: No, score=-0.277 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FORGED_GMAIL_RCVD=1, FREEMAIL_FROM=0.001, NICE_REPLY_A=-0.948, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_SOFTFAIL=0.665, URIBL_BLOCKED=0.001] autolearn=no 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 VdU-jkVKrLjq for ; Thu, 10 Sep 2020 00:08:00 -0700 (PDT) Received: from sainfoin-smtp-out.extra.cea.fr (sainfoin-smtp-out.extra.cea.fr [132.167.192.228]) (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 AFC073A1047 for ; Thu, 10 Sep 2020 00:07:59 -0700 (PDT) Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by sainfoin-sys.extra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id 08A77vLt033353; Thu, 10 Sep 2020 09:07:57 +0200 Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id DFFF0201574; Thu, 10 Sep 2020 09:07:57 +0200 (CEST) Received: from muguet1-smtp-out.intra.cea.fr (muguet1-smtp-out.intra.cea.fr [132.166.192.12]) by pisaure.intra.cea.fr (Postfix) with ESMTP id D1E4D20149B; Thu, 10 Sep 2020 09:07:57 +0200 (CEST) Received: from [10.11.240.228] ([10.11.240.228]) by muguet1-sys.intra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id 08A77v6P021867; Thu, 10 Sep 2020 09:07:57 +0200 To: John Kenney Cc: IPWAVE WG References: From: Alexandre Petrescu Message-ID: <9b780ad5-3892-36ef-762d-58f1d186a94d@gmail.com> Date: Thu, 10 Sep 2020 09:07:56 +0200 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.12.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: fr Content-Transfer-Encoding: 8bit Archived-At: Subject: Re: [ipwave] 802.11bd D1.0 preliminary spec available somewhere? 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Sep 2020 07:08:02 -0000 Hi, John, Thank you for the reply. Does the document mention the word 'IPv6'? (RFC8691?) Alex Le 09/09/2020 à 23:41, John Kenney a écrit : > Hi Alex, > > No, this is a work in progress, scheduled to be completed later this > month. It will be a draft standard. Unless a decision is made to make it > available for sale, it will only be available to IEEE 802.11 WG voting > members. > > Best Regards, > John > > > On Wed, Sep 9, 2020 at 5:49 AM Alexandre Petrescu > > wrote: > > Hi, > > I am looking for the IEEE 802.11bd D1.0 preliminary spec.  Is it > available somewhere I could look at it? > > It is to see whether, hopefully, it cites RFC8691 for IPv6 use. > > Alex > > _______________________________________________ > its mailing list > its@ietf.org > https://www.ietf.org/mailman/listinfo/its > > > > -- > John Kenney > Director and Sr. Principal Researcher > Toyota InfoTech Labs > 465 Bernardo Avenue > Mountain View, CA 94043 > Tel: 650-694-4160. Mobile: 650-224-6644 From nobody Thu Sep 10 02:07:33 2020 Return-Path: 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 645213A1107 for ; Thu, 10 Sep 2020 02:07:32 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.277 X-Spam-Level: X-Spam-Status: No, score=-0.277 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FORGED_GMAIL_RCVD=1, FREEMAIL_FROM=0.001, NICE_REPLY_A=-0.948, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_SOFTFAIL=0.665, URIBL_BLOCKED=0.001] autolearn=no 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 xp9y3Q8dnruD for ; Thu, 10 Sep 2020 02:07:30 -0700 (PDT) Received: from cirse-smtp-out.extra.cea.fr (cirse-smtp-out.extra.cea.fr [132.167.192.148]) (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 8E1D03A124D for ; Thu, 10 Sep 2020 02:07:30 -0700 (PDT) Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by cirse-sys.extra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id 08A97Qbm037893; Thu, 10 Sep 2020 11:07:26 +0200 Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id B5F2720474A; Thu, 10 Sep 2020 11:07:26 +0200 (CEST) Received: from muguet1-smtp-out.intra.cea.fr (muguet1-smtp-out.intra.cea.fr [132.166.192.12]) by pisaure.intra.cea.fr (Postfix) with ESMTP id AC47F204743; Thu, 10 Sep 2020 11:07:26 +0200 (CEST) Received: from [10.8.35.150] (is154594.intra.cea.fr [10.8.35.150]) by muguet1-sys.intra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id 08A97QhX026352; Thu, 10 Sep 2020 11:07:26 +0200 To: dickroy@alum.mit.edu, "'John Kenney'" Cc: "'IPWAVE WG'" References: <9b780ad5-3892-36ef-762d-58f1d186a94d@gmail.com> <04857EE4CB264A50B80347971C0A4030@SRA6> From: Alexandre Petrescu Message-ID: <35a5909e-50b3-49c6-7998-69c809f14b57@gmail.com> Date: Thu, 10 Sep 2020 11:07:26 +0200 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.12.0 MIME-Version: 1.0 In-Reply-To: <04857EE4CB264A50B80347971C0A4030@SRA6> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: fr Content-Transfer-Encoding: 8bit Archived-At: Subject: Re: [ipwave] 802.11bd D1.0 preliminary spec available somewhere? 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Sep 2020 09:07:32 -0000 Le 10/09/2020 à 09:18, Dick Roy a écrit : > Hi Alex, > > FYI ... there is very little if anything in any IEEE 802 LAN > specification that in any way specifies or constrains what happens > in any network layer protocol. (W)LANs operate at layer 2 and > below. IPvx is functionality at layer 3. True enough. However, when looking at details of the specs, it might that 802.11 documents do use the words 'IP' and 'IPv6' in particular. Last time I looked at an 802.11 spec I was successful in searching and finding the word IPv6. That was some years ago. Now the situation is different. The word should be there, but it should cite [RFC 8691] in the case of OCB operation of 802.11. I mean, if the word 'IPv6' is there in the 802.11bd document, then it makes no sense to not cite RFC 8691. If the word 'IPv6' is not there in the 802.11bd document, then indeed it makes sense to not cite RFC 8691. (I would be tempted to suggest the same to ISO TC204 documents but I know you will not agree because I know in your thought this RFC8691 does not fully address one's expectations of fully variable wireless environments of automobile networks; so I dont suggest it for ISO TC 204). Yours, Alex > > Hope this helps... > > RR > > -----Original Message----- From: its [mailto:its-bounces@ietf.org] > On Behalf Of Alexandre Petrescu Sent: Thursday, September 10, 2020 > 12:08 AM To: John Kenney Cc: IPWAVE WG Subject: Re: [ipwave] 802.11bd > D1.0 preliminary spec available somewhere? > > Hi, John, > > Thank you for the reply. > > Does the document mention the word 'IPv6'? (RFC8691?) > > Alex > > Le 09/09/2020 à 23:41, John Kenney a écrit : >> Hi Alex, >> >> No, this is a work in progress, scheduled to be completed later >> this month. It will be a draft standard. Unless a decision is made >> to make it available for sale, it will only be available to IEEE >> 802.11 WG voting members. >> >> Best Regards, John >> >> >> On Wed, Sep 9, 2020 at 5:49 AM Alexandre Petrescu >> > > > wrote: >> >> Hi, >> >> I am looking for the IEEE 802.11bd D1.0 preliminary spec. Is it >> available somewhere I could look at it? >> >> It is to see whether, hopefully, it cites RFC8691 for IPv6 use. >> >> Alex >> >> _______________________________________________ its mailing list >> its@ietf.org >> https://www.ietf.org/mailman/listinfo/its >> >> >> >> -- John Kenney Director and Sr. Principal Researcher Toyota >> InfoTech Labs 465 Bernardo Avenue Mountain View, CA 94043 Tel: >> 650-694-4160. Mobile: 650-224-6644 > > _______________________________________________ its mailing list > its@ietf.org https://www.ietf.org/mailman/listinfo/its > From nobody Thu Sep 10 03:33:03 2020 Return-Path: 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 691DE3A0365 for ; Thu, 10 Sep 2020 03:33:01 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.277 X-Spam-Level: X-Spam-Status: No, score=-0.277 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FORGED_GMAIL_RCVD=1, FREEMAIL_FROM=0.001, NICE_REPLY_A=-0.948, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_SOFTFAIL=0.665, URIBL_BLOCKED=0.001] autolearn=no 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 3uOoH03Q7mvZ for ; Thu, 10 Sep 2020 03:33:00 -0700 (PDT) Received: from cirse-smtp-out.extra.cea.fr (cirse-smtp-out.extra.cea.fr [132.167.192.148]) (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 A7A243A02BC for ; Thu, 10 Sep 2020 03:32:59 -0700 (PDT) Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by cirse-sys.extra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id 08AAWtLv017571; Thu, 10 Sep 2020 12:32:55 +0200 Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 8CC7120483D; Thu, 10 Sep 2020 12:32:55 +0200 (CEST) Received: from muguet1-smtp-out.intra.cea.fr (muguet1-smtp-out.intra.cea.fr [132.166.192.12]) by pisaure.intra.cea.fr (Postfix) with ESMTP id 7B14A2047B8; Thu, 10 Sep 2020 12:32:55 +0200 (CEST) Received: from [10.8.35.150] (is154594.intra.cea.fr [10.8.35.150]) by muguet1-sys.intra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id 08AAWt1M022280; Thu, 10 Sep 2020 12:32:55 +0200 To: dickroy@alum.mit.edu, "'John Kenney'" Cc: "'IPWAVE WG'" References: <9b780ad5-3892-36ef-762d-58f1d186a94d@gmail.com> <04857EE4CB264A50B80347971C0A4030@SRA6> <35a5909e-50b3-49c6-7998-69c809f14b57@gmail.com> From: Alexandre Petrescu Message-ID: <95690a67-566e-9fa8-e73d-12bdeae89593@gmail.com> Date: Thu, 10 Sep 2020 12:32:55 +0200 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.12.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: fr Content-Transfer-Encoding: 8bit Archived-At: Subject: Re: [ipwave] 802.11bd D1.0 preliminary spec available somewhere? 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Sep 2020 10:33:01 -0000 Le 10/09/2020 à 11:41, Dick Roy a écrit : > Standards relevant to layer 3 can and often do mention IP and the > relevant RFCs. Standards relevant to other layers should not have > any need to reference protocols at other layers in ay normative way > ... that's the whole point of the layered model and layer separation. > Any attempts to violate the layer separation principle do so at their > own peril. YEs layer separation, but there are interfaces between layers, right? I mean, if RFC8691 specifies that the MTU must a be of a minimum 1280bytes, then the MAC should satisfy that by fragmenting and reassembling where necessary, if necessary. If RFC8691 says that the frame format below IP must use QoS Data headers then 802.11bd wouldnt say otherwise. If RFC8691 says that the priority value must be '1' in the QoS data header (at the MAC layer) then 802.11bd wouldnt say otherwise, right? Alex > > RR > > -----Original Message----- From: its [mailto:its-bounces@ietf.org] On > Behalf Of Alexandre Petrescu Sent: Thursday, September 10, 2020 2:07 > AM To: dickroy@alum.mit.edu; 'John Kenney' Cc: 'IPWAVE WG' Subject: > Re: [ipwave] 802.11bd D1.0 preliminary spec available somewhere? > > > > Le 10/09/2020 à 09:18, Dick Roy a écrit : >> Hi Alex, >> >> FYI ... there is very little if anything in any IEEE 802 LAN >> specification that in any way specifies or constrains what happens >> in any network layer protocol. (W)LANs operate at layer 2 and >> below. IPvx is functionality at layer 3. > > True enough. > > However, when looking at details of the specs, it might that 802.11 > documents do use the words 'IP' and 'IPv6' in particular. Last time > I looked at an 802.11 spec I was successful in searching and finding > the word IPv6. That was some years ago. > > Now the situation is different. The word should be there, but it > should cite [RFC 8691] in the case of OCB operation of 802.11. > > I mean, if the word 'IPv6' is there in the 802.11bd document, then > it makes no sense to not cite RFC 8691. > > If the word 'IPv6' is not there in the 802.11bd document, then indeed > it makes sense to not cite RFC 8691. > > (I would be tempted to suggest the same to ISO TC204 documents but I > know you will not agree because I know in your thought this RFC8691 > does not fully address one's expectations of fully variable wireless > environments of automobile networks; so I dont suggest it for ISO TC > 204). > > Yours, > > Alex > >> >> Hope this helps... >> >> RR >> >> -----Original Message----- From: its [mailto:its-bounces@ietf.org] >> On Behalf Of Alexandre Petrescu Sent: Thursday, September 10, 2020 >> 12:08 AM To: John Kenney Cc: IPWAVE WG Subject: Re: [ipwave] >> 802.11bd D1.0 preliminary spec available somewhere? >> >> Hi, John, >> >> Thank you for the reply. >> >> Does the document mention the word 'IPv6'? (RFC8691?) >> >> Alex >> >> Le 09/09/2020 à 23:41, John Kenney a écrit : >>> Hi Alex, >>> >>> No, this is a work in progress, scheduled to be completed later >>> this month. It will be a draft standard. Unless a decision is >>> made to make it available for sale, it will only be available to >>> IEEE 802.11 WG voting members. >>> >>> Best Regards, John >>> >>> >>> On Wed, Sep 9, 2020 at 5:49 AM Alexandre Petrescu >>> >> > >> wrote: >>> >>> Hi, >>> >>> I am looking for the IEEE 802.11bd D1.0 preliminary spec. Is it >>> available somewhere I could look at it? >>> >>> It is to see whether, hopefully, it cites RFC8691 for IPv6 use. >>> >>> Alex >>> >>> _______________________________________________ its mailing list >>> its@ietf.org >>> https://www.ietf.org/mailman/listinfo/its >>> >>> >>> >>> -- John Kenney Director and Sr. Principal Researcher Toyota >>> InfoTech Labs 465 Bernardo Avenue Mountain View, CA 94043 Tel: >>> 650-694-4160. Mobile: 650-224-6644 >> >> _______________________________________________ its mailing list >> its@ietf.org https://www.ietf.org/mailman/listinfo/its >> > > _______________________________________________ its mailing list > its@ietf.org https://www.ietf.org/mailman/listinfo/its > From nobody Thu Sep 10 09:26:37 2020 Return-Path: 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 9A9A13A0D9D for ; Thu, 10 Sep 2020 09:26:34 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.847 X-Spam-Level: X-Spam-Status: No, score=-1.847 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_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, 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 j2xbCzUk8PTa for ; Thu, 10 Sep 2020 09:26:32 -0700 (PDT) Received: from mail-il1-x135.google.com (mail-il1-x135.google.com [IPv6:2607:f8b0:4864:20::135]) (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 2A6643A0D83 for ; Thu, 10 Sep 2020 09:26:32 -0700 (PDT) Received: by mail-il1-x135.google.com with SMTP id t13so6217582ile.9 for ; Thu, 10 Sep 2020 09:26:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=aLgAAzGtGVlk4ywtE/LuNPuaOwRjzBTQFpa/c7bE3kE=; b=dL/fIBXkYpZONh+miPTChRrgqP2YyTYG0f4oB0XirvC2OVsBs3anWUjQ1qBWmWQY3v 3iGPXwNVIBvoY/h0a3tPGcDwd4N0yYaKivni0g3bU5fyKEkPrfcEjYQ6LVqTlQnxYVTU 11o2w86mLAsCh+2LeKHOpxhh3GAw5vpfGQSDBeCC44N5ASMD/7l8nFCB8YRri9nSf3qL R58XbqlhrV3LrNWgfF2Il0fZuyNgo416n1C1w2AAJATKsJDx9ffGtIfVhDgcBiDCkHKx CYOFCQfW2maWQXOmBtufA/g0NJv0Flyq780aUKNXYTqqwdYBTnEzwPHa7670I8L/nrah VqQA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=aLgAAzGtGVlk4ywtE/LuNPuaOwRjzBTQFpa/c7bE3kE=; b=HSFhMZ1LN2IyrXzvHimbsWVB6zvwPtaAZ/HpI9fFs6g6s1UQbKNdNnvTYCD7k1nCWL N/YQCgE4Y3i5pQvfv0FQswZZqedXYovCEdk/pj40q946UlSB9KXawW8kPQHxr+3pLyyy fozB2Ug2cIRDrmHHUKS8WYXmzOzygMoDDJXhuHuOiPBOVf15yXUMUTy8W/jmtiSrXgOq TXNH5Pyhq36oMx8i7d7jVfWE+oHaYLm2ZntG+8wA+p8sUHXTq/i9G/KSWemsaiH6vkGC joNrqxBfYNNquZDeaJawKx/2VdlCp48faS62YK0g+pL98KAse++tYDbmzfxCnVGUiLWm kMvg== X-Gm-Message-State: AOAM53349MX8ktukLUrKkdfjisOpmT0b9qOBaY2huaupHG4P9jdDHcHz T0KinwtcXlKxDp8DyF/AOTynbmA7K5PKMe/j7uE= X-Google-Smtp-Source: ABdhPJx7cyTlKG/9eZv94TS3ap2RhXerzTCLRAr4vFP5i21GZ944lSzZ9LJeuq1KCuV1GyphevS4SeswJcTVUo71olI= X-Received: by 2002:a05:6e02:e07:: with SMTP id a7mr8183798ilk.277.1599755191241; Thu, 10 Sep 2020 09:26:31 -0700 (PDT) MIME-Version: 1.0 References: <9b780ad5-3892-36ef-762d-58f1d186a94d@gmail.com> <04857EE4CB264A50B80347971C0A4030@SRA6> <35a5909e-50b3-49c6-7998-69c809f14b57@gmail.com> <95690a67-566e-9fa8-e73d-12bdeae89593@gmail.com> In-Reply-To: <95690a67-566e-9fa8-e73d-12bdeae89593@gmail.com> From: Dorothy Stanley Date: Thu, 10 Sep 2020 09:26:19 -0700 Message-ID: To: Alexandre Petrescu Cc: Richard Roy , John Kenney , IPWAVE WG Content-Type: multipart/alternative; boundary="000000000000e6cfc205aef8071f" Archived-At: Subject: Re: [ipwave] 802.11bd D1.0 preliminary spec available somewhere? 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Sep 2020 16:26:35 -0000 --000000000000e6cfc205aef8071f Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable As John mentioned, P802.11bd D1.0 is still in preparation, and expected to be available soon. See https://tools.ietf.org/html/rfc7241 section 3.3, and in particular *IEEE 802 WG Chairs have the authority to grant membership in their WGs and= can use this authority to grant membership to an IETF WG chair upon request. The IETF WG chair will be provided with access to the username/password for the IEEE 802 WG archives and is permitted to share that information with participants in the IETF WG. Since it is possible to participate in IETF without attending meetings, or even joining a mailing list, IETF WG chairs will provide the information to anyone who requests it. However, since IEEE 802 work in progress is copyrighted, copyright restrictions prohibit incorporating material into IETF documents or postings.* If access to P802.11bd D1.0 and related drafts is needed to support IPWAVE WG work, the IPWAVE WG Chair should send me the corresponding request. Thanks, Dorothy ---------------------- Dorothy Stanley IEEE 802.11 WG Chair, dstanley@ieee.org Hewlett Packard Enterprise dorothy.stanley@hpe.com dstanley1389@gmail.com +1 630-363-1389 <630-363-1389> On Thu, Sep 10, 2020 at 3:33 AM Alexandre Petrescu < alexandre.petrescu@gmail.com> wrote: > > > Le 10/09/2020 =C3=A0 11:41, Dick Roy a =C3=A9crit : > > Standards relevant to layer 3 can and often do mention IP and the > > relevant RFCs. Standards relevant to other layers should not have > > any need to reference protocols at other layers in ay normative way > > ... that's the whole point of the layered model and layer separation. > > Any attempts to violate the layer separation principle do so at their > > own peril. > > YEs layer separation, but there are interfaces between layers, right? > > I mean, if RFC8691 specifies that the MTU must a be of a minimum > 1280bytes, then the MAC should satisfy that by fragmenting and > reassembling where necessary, if necessary. > > If RFC8691 says that the frame format below IP must use QoS Data headers > then 802.11bd wouldnt say otherwise. > > If RFC8691 says that the priority value must be '1' in the QoS data > header (at the MAC layer) then 802.11bd wouldnt say otherwise, right? > > Alex > > > > > RR > > > > -----Original Message----- From: its [mailto:its-bounces@ietf.org] On > > Behalf Of Alexandre Petrescu Sent: Thursday, September 10, 2020 2:07 > > AM To: dickroy@alum.mit.edu; 'John Kenney' Cc: 'IPWAVE WG' Subject: > > Re: [ipwave] 802.11bd D1.0 preliminary spec available somewhere? > > > > > > > > Le 10/09/2020 =C3=A0 09:18, Dick Roy a =C3=A9crit : > >> Hi Alex, > >> > >> FYI ... there is very little if anything in any IEEE 802 LAN > >> specification that in any way specifies or constrains what happens > >> in any network layer protocol. (W)LANs operate at layer 2 and > >> below. IPvx is functionality at layer 3. > > > > True enough. > > > > However, when looking at details of the specs, it might that 802.11 > > documents do use the words 'IP' and 'IPv6' in particular. Last time > > I looked at an 802.11 spec I was successful in searching and finding > > the word IPv6. That was some years ago. > > > > Now the situation is different. The word should be there, but it > > should cite [RFC 8691] in the case of OCB operation of 802.11. > > > > I mean, if the word 'IPv6' is there in the 802.11bd document, then > > it makes no sense to not cite RFC 8691. > > > > If the word 'IPv6' is not there in the 802.11bd document, then indeed > > it makes sense to not cite RFC 8691. > > > > (I would be tempted to suggest the same to ISO TC204 documents but I > > know you will not agree because I know in your thought this RFC8691 > > does not fully address one's expectations of fully variable wireless > > environments of automobile networks; so I dont suggest it for ISO TC > > 204). > > > > Yours, > > > > Alex > > > >> > >> Hope this helps... > >> > >> RR > >> > >> -----Original Message----- From: its [mailto:its-bounces@ietf.org] > >> On Behalf Of Alexandre Petrescu Sent: Thursday, September 10, 2020 > >> 12:08 AM To: John Kenney Cc: IPWAVE WG Subject: Re: [ipwave] > >> 802.11bd D1.0 preliminary spec available somewhere? > >> > >> Hi, John, > >> > >> Thank you for the reply. > >> > >> Does the document mention the word 'IPv6'? (RFC8691?) > >> > >> Alex > >> > >> Le 09/09/2020 =C3=A0 23:41, John Kenney a =C3=A9crit : > >>> Hi Alex, > >>> > >>> No, this is a work in progress, scheduled to be completed later > >>> this month. It will be a draft standard. Unless a decision is > >>> made to make it available for sale, it will only be available to > >>> IEEE 802.11 WG voting members. > >>> > >>> Best Regards, John > >>> > >>> > >>> On Wed, Sep 9, 2020 at 5:49 AM Alexandre Petrescu > >>> >>> > > >> wrote: > >>> > >>> Hi, > >>> > >>> I am looking for the IEEE 802.11bd D1.0 preliminary spec. Is it > >>> available somewhere I could look at it? > >>> > >>> It is to see whether, hopefully, it cites RFC8691 for IPv6 use. > >>> > >>> Alex > >>> > >>> _______________________________________________ its mailing list > >>> its@ietf.org > >>> https://www.ietf.org/mailman/listinfo/its > >>> > >>> > >>> > >>> -- John Kenney Director and Sr. Principal Researcher Toyota > >>> InfoTech Labs 465 Bernardo Avenue Mountain View, CA 94043 Tel: > >>> 650-694-4160. Mobile: 650-224-6644 > >> > >> _______________________________________________ its mailing list > >> its@ietf.org https://www.ietf.org/mailman/listinfo/its > >> > > > > _______________________________________________ its mailing list > > its@ietf.org https://www.ietf.org/mailman/listinfo/its > > > > _______________________________________________ > its mailing list > its@ietf.org > https://www.ietf.org/mailman/listinfo/its > --000000000000e6cfc205aef8071f Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
As John mentioned, P802.11bd D1.0 is still in prepara= tion, and expected to be available soon.

See https://tools.ietf.org/html/rfc7= 241 section 3.3, and in particular
IEEE 802 WG Chairs have the authority to gr=
ant membership in their WGs and can
   use this authority to grant membership to an IETF WG chair upon
   request.  The IETF WG chair will be provided with access to the
   username/password for the IEEE 802 WG archives and is permitted to
   share that information with participants in the IETF WG.  Since it is
   possible to participate in IETF without attending meetings, or even
   joining a mailing list, IETF WG chairs will provide the information
   to anyone who requests it.  However, since IEEE 802 work in progress
   is copyrighted, copyright restrictions prohibit incorporating
   material into IETF documents or postings.
If access to P802.11bd D1.0 and related drafts is needed to supp= ort IPWAVE WG work, the
IPWAVE WG Chair should send me the corres= ponding request.

Thanks,

= Dorothy
<= div dir=3D"ltr">

----------------------
Dorothy Stanley
IEEE 802.11 WG Chair,
dstanley@ieee.orgHewlett Packard Enterprise
dorothy.stanley@hpe.com
dstanley138= 9@gmail.com
+1 630-363-1389

=


<= div dir=3D"ltr" class=3D"gmail_attr">On Thu, Sep 10, 2020 at 3:33 AM Alexan= dre Petrescu <alexandre.= petrescu@gmail.com> wrote:


Le 10/09/2020 =C3=A0 11:41, Dick Roy a =C3=A9crit :
> Standards relevant to layer 3 can and often do mention IP and the
> relevant RFCs.=C2=A0 Standards relevant to other layers should not hav= e
> any need to reference protocols at other layers in ay normative way > ... that's the whole point of the layered model and layer separati= on.
> Any attempts to violate the layer separation principle do so at their<= br> > own peril.

YEs layer separation, but there are interfaces between layers, right?

I mean, if RFC8691 specifies that the MTU must a be of a minimum
1280bytes, then the MAC should satisfy that by fragmenting and
reassembling where necessary, if necessary.

If RFC8691 says that the frame format below IP must use QoS Data headers then 802.11bd wouldnt say otherwise.

If RFC8691 says that the priority value must be '1' in the QoS data=
header (at the MAC layer) then 802.11bd wouldnt say otherwise, right?

Alex

>
> RR
>
> -----Original Message----- From: its [mailto:its-bounces@ietf.org] On
> Behalf Of Alexandre Petrescu Sent: Thursday, September 10, 2020 2:07 > AM To: dickr= oy@alum.mit.edu; 'John Kenney' Cc: 'IPWAVE WG' Subject:=
> Re: [ipwave] 802.11bd D1.0 preliminary spec available somewhere?
>
>
>
> Le 10/09/2020 =C3=A0 09:18, Dick Roy a =C3=A9crit :
>> Hi Alex,
>>
>> FYI ... there is very little if anything in any IEEE 802 LAN
>> specification that in any way specifies or constrains what happens=
>> in any network layer protocol.=C2=A0 (W)LANs operate at layer 2 an= d
>> below. IPvx is functionality at layer 3.
>
> True enough.
>
> However, when looking at details of the specs, it might that 802.11 > documents do use the words 'IP' and 'IPv6' in particul= ar.=C2=A0 Last time
> I looked at an 802.11 spec I was successful in searching and finding > the word IPv6.=C2=A0 That was some years ago.
>
> Now the situation is different.=C2=A0 The word should be there, but it=
> should cite [RFC 8691] in the case of OCB operation of 802.11.
>
> I mean, if the word 'IPv6' is there in the 802.11bd document, = then
> it makes no sense to not cite RFC 8691.
>
> If the word 'IPv6' is not there in the 802.11bd document, then= indeed
> it makes sense to not cite RFC 8691.
>
> (I would be tempted to suggest the same to ISO TC204 documents but I <= br> > know you will not agree because I know in your thought this RFC8691 > does not fully address one's expectations of fully variable wirele= ss
> environments of automobile networks; so I dont suggest it for ISO TC > 204).
>
> Yours,
>
> Alex
>
>>
>> Hope this helps...
>>
>> RR
>>
>> -----Original Message----- From: its [mailto:its-bounces@ietf.org]
>> On Behalf Of Alexandre Petrescu Sent: Thursday, September 10, 2020=
>> 12:08 AM To: John Kenney Cc: IPWAVE WG Subject: Re: [ipwave]
>> 802.11bd D1.0 preliminary spec available somewhere?
>>
>> Hi, John,
>>
>> Thank you for the reply.
>>
>> Does the document mention the word 'IPv6'? (RFC8691?)
>>
>> Alex
>>
>> Le 09/09/2020 =C3=A0 23:41, John Kenney a =C3=A9crit :
>>> Hi Alex,
>>>
>>> No, this is a work in progress, scheduled to be completed late= r
>>> this month. It will be a draft standard. Unless a decision is<= br> >>> made to make it available for sale, it will only be available = to
>>> IEEE 802.11 WG voting members.
>>>
>>> Best Regards, John
>>>
>>>
>>> On Wed, Sep 9, 2020 at 5:49 AM Alexandre Petrescu
>>> <alexandre.petrescu@gmail.com
>>> <mailto:alexandre.petrescu@gmail.com>>
>> wrote:
>>>
>>> Hi,
>>>
>>> I am looking for the IEEE 802.11bd D1.0 preliminary spec.=C2= =A0 Is it
>>> available somewhere I could look at it?
>>>
>>> It is to see whether, hopefully, it cites RFC8691 for IPv6 use= .
>>>
>>> Alex
>>>
>>> _______________________________________________ its mailing li= st
>>> its@ietf.org= <mailto:its@ietf.= org>
>>> https://www.ietf.org/mailman/listinfo/its<= br> >>>
>>>
>>>
>>> -- John Kenney Director and Sr. Principal Researcher Toyota >>> InfoTech Labs 465 Bernardo Avenue Mountain View, CA 94043 Tel:=
>>> 650-694-4160. Mobile: 650-224-6644
>>
>> _______________________________________________ its mailing list <= br> >> its@ietf.org= https://www.ietf.org/mailman/listinfo/its
>>
>
> _______________________________________________ its mailing list
> its@ietf.org https://www.ietf.org/mailman/listinfo/its
>

_______________________________________________
its mailing list
its@ietf.org
https://www.ietf.org/mailman/listinfo/its
--000000000000e6cfc205aef8071f-- From nobody Thu Sep 10 09:49:28 2020 Return-Path: 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 66EFA3A03F5 for ; Thu, 10 Sep 2020 09:49:26 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.898 X-Spam-Level: X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=us-toyota-itc-com.20150623.gappssmtp.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 d_JcXf3QNlxL for ; Thu, 10 Sep 2020 09:49:24 -0700 (PDT) Received: from mail-yb1-xb2f.google.com (mail-yb1-xb2f.google.com [IPv6:2607:f8b0:4864:20::b2f]) (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 C197B3A0128 for ; Thu, 10 Sep 2020 09:49:24 -0700 (PDT) Received: by mail-yb1-xb2f.google.com with SMTP id c17so4524451ybe.0 for ; Thu, 10 Sep 2020 09:49:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=us-toyota-itc-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=HqUD3or+Ce0tSZ48j2T93W5ZJU+RKueijK3eXVWuHE4=; b=IJNR04dWd28gJSbn3Q7FLEw3NtV+F79Cgwomofy/1dRTwm5vdTo1dh5ty3hJu6O1PM aqoUu/0wI12ivjYs0N+LVYnXThtu7hb9T8BBPCMkSa/sNr98M56rGtVVRs6V2TouN0pP 49aAvMO0JFXRkL84f4kMX8WMTL96NJVCCEAmDXxuaWFcQhGlMdiJ2NjnFHpvnfomyg4G WAxZuqJW9kr1fM5ZD0dDT6FVFl5lNNx/HSz1vhHXYtpedDujktGBXGKwdy4mMXN2/VNs qrETJuxn6E/i8cmGfxl/REddcq3oZ0I6SHIfMyzj+7zpL4t+9d+z7kcbtqWNyfm6bJrL 4hZQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=HqUD3or+Ce0tSZ48j2T93W5ZJU+RKueijK3eXVWuHE4=; b=K6ojiayZZ5e14i26rzIywAmCsncjqK2NZO7/ZilCt1OUKv4NslmLSua4RGSZ6Hx3nr sWVd1XrkUgTPmvrQ9A+PBAlPqV3NUkZdyykCeF34sHJMcIb1aKAg/nYpKe9CfKMhbx0n JkbhWMM7GCIaOBQpgbawEsyvM9P/GHCQX8LzCHmiq49Qfm33BLyjwwkNVBoVDVzBiCJr 7R+KGREpqu672gxgB1+AbZihR1b069b9rCL8Vj14TWSQV/3/W4+/8/GFpcLNBWSuKJ1t X3B73/2r1W9RK+54IZjgZN2Chp6sz04aYu3PjgB1IUpDUWbQTxcwcwqRX7QkWWYLaiXx 0Qsw== X-Gm-Message-State: AOAM530nHTcMy0E6Oq3kEH7K3e1XzoXVvBEg0+pTZd0TMoy49/TtsiyB SJgprunnkP3Pqt/9on+xQs3jramGpTZp5SDymA8dUA== X-Google-Smtp-Source: ABdhPJzbzFGcSf1athmSWqydOtGBfjkUhTWhva4fa3x3O+iHxzPSC646vetyc1TeSNnsDxlyo1isCmc4BjBEOKZcW4g= X-Received: by 2002:a25:5887:: with SMTP id m129mr15464767ybb.11.1599756563797; Thu, 10 Sep 2020 09:49:23 -0700 (PDT) MIME-Version: 1.0 References: <9b780ad5-3892-36ef-762d-58f1d186a94d@gmail.com> In-Reply-To: <9b780ad5-3892-36ef-762d-58f1d186a94d@gmail.com> From: John Kenney Date: Thu, 10 Sep 2020 09:49:28 -0700 Message-ID: To: Alexandre Petrescu Cc: IPWAVE WG Content-Type: multipart/alternative; boundary="000000000000b672dc05aef8595b" Archived-At: Subject: Re: [ipwave] 802.11bd D1.0 preliminary spec available somewhere? 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Sep 2020 16:49:27 -0000 --000000000000b672dc05aef8595b Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable HI Alex, No. The draft amendment does not add any new references to 802.11. TGbd, the 802.11 task group developing the amendment, has regular teleconferences. The teleconference schedule for all 802.11 task groups can be found in the lower right corner of this site . These are open meetings, and all are welcome to participate. Best Regards, John On Thu, Sep 10, 2020 at 12:08 AM Alexandre Petrescu < alexandre.petrescu@gmail.com> wrote: > Hi, John, > > Thank you for the reply. > > Does the document mention the word 'IPv6'? (RFC8691?) > > Alex > > Le 09/09/2020 =C3=A0 23:41, John Kenney a =C3=A9crit : > > Hi Alex, > > > > No, this is a work in progress, scheduled to be completed later this > > month. It will be a draft standard. Unless a decision is made to make i= t > > available for sale, it will only be available to IEEE 802.11 WG voting > > members. > > > > Best Regards, > > John > > > > > > On Wed, Sep 9, 2020 at 5:49 AM Alexandre Petrescu > > > > wrote: > > > > Hi, > > > > I am looking for the IEEE 802.11bd D1.0 preliminary spec. Is it > > available somewhere I could look at it? > > > > It is to see whether, hopefully, it cites RFC8691 for IPv6 use. > > > > Alex > > > > _______________________________________________ > > its mailing list > > its@ietf.org > > https://www.ietf.org/mailman/listinfo/its > > > > > > > > -- > > John Kenney > > Director and Sr. Principal Researcher > > Toyota InfoTech Labs > > 465 Bernardo Avenue > > Mountain View, CA 94043 > > Tel: 650-694-4160. Mobile: 650-224-6644 > --=20 John Kenney Director and Sr. Principal Researcher Toyota InfoTech Labs 465 Bernardo Avenue Mountain View, CA 94043 Tel: 650-694-4160. Mobile: 650-224-6644 --000000000000b672dc05aef8595b Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
HI Alex,
No. The draft amendment does not add any new = references to 802.11.=C2=A0=C2=A0

TGbd, the 802.11= task group developing the amendment, has regular teleconferences.=C2=A0 Th= e teleconference schedule for all 802.11 task groups can be found in the lo= wer right corner of this site.= =C2=A0These are open meetings, and all are welcome to participate.

Best Regards,
John


=


On Thu, Sep 10, 2020 at 12:08 AM Alexandre Petrescu &l= t;alexandre.petrescu@gmail.= com> wrote:
Hi, John,

Thank you for the reply.

Does the document mention the word 'IPv6'? (RFC8691?)

Alex

Le 09/09/2020 =C3=A0 23:41, John Kenney a =C3=A9crit=C2=A0:
> Hi Alex,
>
> No, this is a work in progress, scheduled to be completed later this <= br> > month. It will be a draft standard. Unless a decision is made to make = it
> available for sale, it will only be available to IEEE 802.11 WG voting=
> members.
>
> Best Regards,
> John
>
>
> On Wed, Sep 9, 2020 at 5:49 AM Alexandre Petrescu
> <= alexandre.petrescu@gmail.com <mailto:alexandre.petrescu@gmail.com>>= wrote:
>
>=C2=A0 =C2=A0 =C2=A0Hi,
>
>=C2=A0 =C2=A0 =C2=A0I am looking for the IEEE 802.11bd D1.0 preliminary= spec.=C2=A0 Is it
>=C2=A0 =C2=A0 =C2=A0available somewhere I could look at it?
>
>=C2=A0 =C2=A0 =C2=A0It is to see whether, hopefully, it cites RFC8691 f= or IPv6 use.
>
>=C2=A0 =C2=A0 =C2=A0Alex
>
>=C2=A0 =C2=A0 =C2=A0_______________________________________________
>=C2=A0 =C2=A0 =C2=A0its mailing list
>=C2=A0 =C2=A0 =C2=A0i= ts@ietf.org <mailto:its@ietf.org>
>=C2=A0 =C2=A0 =C2=A0https://www.ietf.org/mailman/listin= fo/its
>
>
>
> --
> John Kenney
> Director and Sr. Principal Researcher
> Toyota InfoTech Labs
> 465 Bernardo Avenue
> Mountain View, CA 94043
> Tel: 650-694-4160. Mobile: 650-224-6644


--
John Kenney
Director and Sr. Principal Researcher
Toyota InfoTech Labs
465 Bernardo Avenue
Mountain View, CA 94043
Tel: 650-694-4160. Mobile: 650-224-6644
<= /div>
--000000000000b672dc05aef8595b-- From nobody Fri Sep 11 05:28:05 2020 Return-Path: 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 4F1543A0FC3 for ; Fri, 11 Sep 2020 05:27:51 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.277 X-Spam-Level: X-Spam-Status: No, score=-0.277 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FORGED_GMAIL_RCVD=1, FREEMAIL_FROM=0.001, NICE_REPLY_A=-0.948, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_SOFTFAIL=0.665, URIBL_BLOCKED=0.001] autolearn=no 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 90pIpsje9Zq1 for ; Fri, 11 Sep 2020 05:27:49 -0700 (PDT) Received: from sainfoin-smtp-out.extra.cea.fr (sainfoin-smtp-out.extra.cea.fr [132.167.192.228]) (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 6A3923A0FB6 for ; Fri, 11 Sep 2020 05:27:49 -0700 (PDT) Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by sainfoin-sys.extra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id 08BCRlBP011854; Fri, 11 Sep 2020 14:27:47 +0200 Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 4B288204965; Fri, 11 Sep 2020 14:27:47 +0200 (CEST) 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 3353B204976; Fri, 11 Sep 2020 14:27:47 +0200 (CEST) Received: from [10.8.35.150] (is154594.intra.cea.fr [10.8.35.150]) by muguet2-sys.intra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id 08BCRl5B011262; Fri, 11 Sep 2020 14:27:47 +0200 To: John Kenney Cc: IPWAVE WG References: <9b780ad5-3892-36ef-762d-58f1d186a94d@gmail.com> From: Alexandre Petrescu Message-ID: <3f2f173c-1c5d-ecdf-623f-b59e3f60522a@gmail.com> Date: Fri, 11 Sep 2020 14:27:47 +0200 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.12.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: fr Content-Transfer-Encoding: 8bit Archived-At: Subject: Re: [ipwave] 802.11bd D1.0 preliminary spec available somewhere? 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Sep 2020 12:28:04 -0000 Le 10/09/2020 à 18:49, John Kenney a écrit : > HI Alex, > No. The draft amendment does not add any new references to 802.11. > > TGbd, the 802.11 task group developing the amendment, has regular > teleconferences.  The teleconference schedule for all 802.11 task groups > can be found in the lower right corner of this site > . These are open meetings, and all are > welcome to participate. Thanks, It seems the next one is today at 16h Paris time. https://ieeesa.webex.com/ieeesa/j.php?MTID=m87469a9d84a11170705c33bc1f782b97 LieuWebex-11a: 129 513 9746 (plan) DescriptionJoin the Webex meeting here: https://ieeesa.webex.com/ieeesa/j.php?MTID=m87469a9d84a11170705c33bc1f782b97 Meeting number: 129 513 9746 Meeting password: wireless (94735377 from phones and video systems) Join by phone: Tap to call in from a mobile device (attendees only) +1-408-418-9388 USA Toll Global call-in numbers Access code: 129 513 9746 Join from a video system or application Dial 1295139746@ieeesa.webex.com You can also dial 173.243.2.68 and enter your meeting number. Join using Microsoft Lync or Microsoft Skype for Business Dial 1295139746.ieeesa@lync.webex.com Need help? Go to http://help.webex.com plus d'infos» copier dans mon agenda Numéro de la réunion : 129 513 9746 Mot de passe : Veuillez demander le mot de passe de la réunion à l’organisateur. Plus de moyens pour rejoindre les réunions Rejoindre par système vidéo Composer : 1295139746@ieeesa.webex.com Vous pouvez également composer 173.243.2.68 et saisir votre numéro de votre réunion. Rejoindre par téléphone +1-646-992-2010 United States Toll (New York City) +1-213-306-3065 United States Toll (Los Angeles) Code d'accès : 129 513 9746 Numéros d'appel internationaux Alex > > Best Regards, > John > > > > > On Thu, Sep 10, 2020 at 12:08 AM Alexandre Petrescu > > wrote: > > Hi, John, > > Thank you for the reply. > > Does the document mention the word 'IPv6'? (RFC8691?) > > Alex > > Le 09/09/2020 à 23:41, John Kenney a écrit : > > Hi Alex, > > > > No, this is a work in progress, scheduled to be completed later this > > month. It will be a draft standard. Unless a decision is made to > make it > > available for sale, it will only be available to IEEE 802.11 WG > voting > > members. > > > > Best Regards, > > John > > > > > > On Wed, Sep 9, 2020 at 5:49 AM Alexandre Petrescu > > > >> wrote: > > > >     Hi, > > > >     I am looking for the IEEE 802.11bd D1.0 preliminary spec.  Is it > >     available somewhere I could look at it? > > > >     It is to see whether, hopefully, it cites RFC8691 for IPv6 use. > > > >     Alex > > > >     _______________________________________________ > >     its mailing list > > its@ietf.org > > > https://www.ietf.org/mailman/listinfo/its > > > > > > > > -- > > John Kenney > > Director and Sr. Principal Researcher > > Toyota InfoTech Labs > > 465 Bernardo Avenue > > Mountain View, CA 94043 > > Tel: 650-694-4160. Mobile: 650-224-6644 > > > > -- > John Kenney > Director and Sr. Principal Researcher > Toyota InfoTech Labs > 465 Bernardo Avenue > Mountain View, CA 94043 > Tel: 650-694-4160. Mobile: 650-224-6644 From nobody Sat Sep 12 00:00:37 2020 Return-Path: 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 442793A0E32; Sat, 12 Sep 2020 00:00:36 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.096 X-Spam-Level: X-Spam-Status: No, score=-2.096 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, HK_NAME_FM_MR_MRS=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, 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 NutZnbAu_lLD; Sat, 12 Sep 2020 00:00:34 -0700 (PDT) Received: from mail-lf1-x135.google.com (mail-lf1-x135.google.com [IPv6:2a00:1450:4864:20::135]) (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 6F3CA3A0E2C; Sat, 12 Sep 2020 00:00:34 -0700 (PDT) Received: by mail-lf1-x135.google.com with SMTP id y11so8086608lfl.5; Sat, 12 Sep 2020 00:00:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=T8rfFCcyoPn8n7rEK8e+xAOH1jVKNJU6NVE0NoSH5Lk=; b=QkYb62yCPDadcfIrNSN7H5b3JrFlAIMLJynAlokAxxHBrcUnoICzQsuOGjHkz5G4vJ 1oIC12Q/ufzAKSzJ7Dngz36gHI18QWU/yN7NSk/4kyvSFFB1i+IOpvpVmHSy9RC5c1sF Xy9lUC58bLf00PWQsQn5UymuqbURcrnEgLlg1S3kG8Q1JTGZGN/Q0QgEmsxYlAfxigL8 vFFQ3r5aNtR1UiU9GNA3iBadUDnqPbpRoINQH2vXzgab3el7CTCRaAS9lZZBsLJqavj+ V8X14mvPBtOy/4pmTOcAa5P+R707I1LMGLVDBKmMxGLNorP88iuEspL8+1OSvG2wSs1b Xa3w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=T8rfFCcyoPn8n7rEK8e+xAOH1jVKNJU6NVE0NoSH5Lk=; b=STq6IrAPdZL91LEMzAmlcDPywPxzziaoFDMwyPMdLU6fSooCoBqfN7xcB9IIEHlDmK W7eWPmmDNU/gnwiBJ1TZoVL6ArqnzQimqytP/5CLgtozFHwBO8k2eFwrrvslT5SnzFl+ D+mdPHP7+QQyE68jVDIYD3FEIDPb6uUy1dutQSwgTv8IAGoJbNov7k7b/uottiuo6enk ad6APw4O0maJIwWJhkQqyiMQ00ysoa0f6BTBsBYZ6MWtU9TWHxk0MBTtNSIamvo9zvVA oKYuE46Erh9Mf/Dm75vY8r/4G0nvAnIUj8xyREwrBtlakOLAiijCK/mnzr3VFvH3T+Zm jmkw== X-Gm-Message-State: AOAM530adVi9h1ix6USzJJRo8XBsLUh8UrOUkp9zX7nPe7OBM0UsUpS0 FDkwcSC1cjw+zxdol4FOYELnkl1+oEYEGIqfGEq3bDYqttc= X-Google-Smtp-Source: ABdhPJyWH2cmYP8lJ9Ww4YhomnqKEoRvmDH4nCG/G0AOL7hbOapcn9HNT8DC3XQpL3IvkoELGw3VayewoCGOXOdZTis= X-Received: by 2002:a19:6042:: with SMTP id p2mr1249631lfk.458.1599894032275; Sat, 12 Sep 2020 00:00:32 -0700 (PDT) MIME-Version: 1.0 References: <159700346574.3847.5747250447145811268@ietfa.amsl.com> In-Reply-To: <159700346574.3847.5747250447145811268@ietfa.amsl.com> From: "Mr. Jaehoon Paul Jeong" Date: Sat, 12 Sep 2020 15:59:51 +0900 Message-ID: To: Russ Housley via Datatracker , Carlos Bernardos Cc: Erik Kline , its@ietf.org, skku-iotlab-members , "Mr. Jaehoon Paul Jeong" Content-Type: multipart/alternative; boundary="00000000000078ddf805af185b7d" Archived-At: Subject: Re: [ipwave] Publication has been requested for draft-ietf-ipwave-vehicular-networking-19 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 12 Sep 2020 07:00:36 -0000 --00000000000078ddf805af185b7d Content-Type: text/plain; charset="UTF-8" Hi Russ and Carlos, As you may see, there is no progress on our IPWAVE PS draft, which was submitted to the IESG for RFC publication 1.5 months ago. Could you ask our AD to take care of this draft to move forward? Thanks. Best Regards, Paul On Mon, Aug 10, 2020 at 5:05 AM Russ Housley via Datatracker < noreply@ietf.org> wrote: > Russ Housley has requested publication of > draft-ietf-ipwave-vehicular-networking-19 as Informational on behalf of the > IPWAVE working group. > > Please verify the document's state at > https://datatracker.ietf.org/doc/draft-ietf-ipwave-vehicular-networking/ > > > _______________________________________________ > its mailing list > its@ietf.org > https://www.ietf.org/mailman/listinfo/its > -- =========================== Mr. Jaehoon (Paul) Jeong, Ph.D. Associate Professor Department of Computer Science and Engineering Sungkyunkwan University Office: +82-31-299-4957 Email: jaehoon.paul@gmail.com, pauljeong@skku.edu Personal Homepage: http://iotlab.skku.edu/people-jaehoon-jeong.php --00000000000078ddf805af185b7d Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi Russ and Carlos,
As you may see, there is no progre= ss on our IPWAVE PS draft,=C2=A0which
was submitted to the IESG f= or RFC publication 1.5 months ago.

Could you ask o= ur AD to take care of this draft to move forward?

= Thanks.

Best Regards,
Paul
On Mon, = Aug 10, 2020 at 5:05 AM Russ Housley via Datatracker <noreply@ietf.org> wrote:
Russ Housley has requested publication of= draft-ietf-ipwave-vehicular-networking-19 as Informational on behalf of th= e IPWAVE working group.

Please verify the document's state at https://datatracker.ietf.org/doc/draft-ietf-ipwave-vehicular-= networking/


_______________________________________________
its mailing list
its@ietf.org
https://www.ietf.org/mailman/listinfo/its


--
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
Mr. Jaehoon (Paul) Jeong, Ph.= D.
Associate Professor
Department of Computer Science and Engineering=
Sungkyunkwan University
Office: +82-31-299-4957
Email: jaehoon.paul@gmail.com,=C2=A0pauljeong@skku.edu
Personal Homepage: http://iotl= ab.skku.edu/people-jaehoon-jeong.php
<= /div>
--00000000000078ddf805af185b7d-- From nobody Sat Sep 19 09:31:21 2020 Return-Path: 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 B812F3A0BA0 for ; Sat, 19 Sep 2020 09:31:19 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 0.648 X-Spam-Level: X-Spam-Status: No, score=0.648 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FORGED_GMAIL_RCVD=1, FREEMAIL_FROM=0.001, NICE_REPLY_A=-0.001, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_NONE=0.001, SPF_SOFTFAIL=0.665, URIBL_BLOCKED=0.001] autolearn=no 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 d7vBG3YlXLgo for ; Sat, 19 Sep 2020 09:31:18 -0700 (PDT) Received: from cirse-smtp-out.extra.cea.fr (cirse-smtp-out.extra.cea.fr [132.167.192.148]) (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 A5A063A0B9D for ; Sat, 19 Sep 2020 09:31:17 -0700 (PDT) Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by cirse-sys.extra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id 08JGVFl1030573 for ; Sat, 19 Sep 2020 18:31:15 +0200 Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id A2DAC20399B for ; Sat, 19 Sep 2020 18:31:15 +0200 (CEST) Received: from muguet1-smtp-out.intra.cea.fr (muguet1-smtp-out.intra.cea.fr [132.166.192.12]) by pisaure.intra.cea.fr (Postfix) with ESMTP id 98B32200CCB for ; Sat, 19 Sep 2020 18:31:15 +0200 (CEST) Received: from [10.11.240.2] ([10.11.240.2]) by muguet1-sys.intra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id 08JGVFEl019483 for ; Sat, 19 Sep 2020 18:31:15 +0200 To: its@ietf.org References: <8a6a78ab29704f28a21eb483ae406910@boeing.com> <658b27943f9d4b1db2cd28d10fc7c7ff@boeing.com> <389ada57-38dd-25f1-6d52-a3dc9672c42c@gmail.com> From: Alexandre Petrescu Message-ID: Date: Sat, 19 Sep 2020 18:31:14 +0200 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.2.2 MIME-Version: 1.0 In-Reply-To: <389ada57-38dd-25f1-6d52-a3dc9672c42c@gmail.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: fr Content-Transfer-Encoding: 8bit Archived-At: Subject: Re: [ipwave] Flying cars and taxi one step closer to reality 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 19 Sep 2020 16:31:20 -0000 I learned about a new demo by Sky Drive Inc, model SD-03, on Toyota test field in Japan, shown on August 31st, 2020. https://www.lifo.gr/now/tech_science/294406/iaponia-epandromeno-iptameno-aytokinito-petakse-me-epityxia-pote-tha-vgei-stin-paragogi-vinteo (the content of the URL is in Greek) There is a person on-board who pilots the flight (he is not just transported like in e.g. Ehang demo). The article says production is epxected by year 2023. Alex Le 22/10/2019 à 16:01, Alexandre Petrescu a écrit : > Fred, > > I would like to know whether somebody came up with groups of such flying > taxis or VTOLs, like when they came up with 'platoon's of convoyed cars > on the ground? > > Alex > > Le 19/09/2019 à 17:51, Templin (US), Fred L a écrit : >> Alex, Urban Air Mobility is indeed inevitable and will be the vertical >> component >> >> of an integrated 3D its landscape. Thanks for the pointer. >> >> Fred >> >> *From:*Alexandre Petrescu [mailto:alexandre.petrescu@gmail.com] >> *Sent:* Thursday, September 19, 2019 1:22 AM >> *To:* Templin (US), Fred L ; its@ietf.org >> *Subject:* Re: [ipwave] Flying cars and taxi one step closer to reality >> >> SEveral companies do more and more flying taxis, now safely with >> people on board.  It takes some courage, but it's a wider audience now. >> >> 3. France 2 Telematin samedi 14 octobre "Futur du Transport Urbain", à >> partir du 2:48:36 dela video >> https://www.france.tv/france-2/telematin/1060857-telematin.html >> >> Le 24/01/2019 à 16:34, Templin (US), Fred L a écrit : >> >>     Hi Alex, >> >>         -----Original Message----- >> >>         From: its [mailto:its-bounces@ietf.org] On Behalf Of Alexandre >> Petrescu >> >>         Sent: Thursday, January 24, 2019 3:47 AM >> >>         To:its@ietf.org  >> >>         Subject: Re: [ipwave] Flying cars and taxi one step closer to >> reality >> >>         Impressive, >> >>     Thanks. >> >>         The kind of thrill seeing these videos is similar to seeing >> (manned) >> >>         first plane vertical take-offs. >> >>         Airbus also featured air taxi ambitious concepts (cartoons) on >> youtube >> >>         since almost two years. >> >>         A company named AKKA in Europe proposes a similar concept of >> more of a >> >>         plane (horizontal take-off) which self-... flies. >> >>         The Dubai air taxi did fly a year ago, but there was no human >> inside, so >> >>         one legitimately wonders whether it could actually carry that >> much weight. >> >>         The new thing about the boeing video is that we see larger >> propellers >> >>         and a dummy body inside (hopefully weighted).  It seems much >> closer to >> >>         implementations.  Impressive. >> >>         The next step would be to see a human take responsibility of >> sitting on >> >>         the drone while lifting a few meters above ground.  Like in >> what they >> >>         did with first elevator in NYC, first man in first plane, bridge >> >>         engineer first walk on bridge, agency director first liftoff >> towards >> >>         first man in space, etc.  Until then one still doubts :-) >> >>     Already been done, and a long time ago (Lunar Landing Research >> >>     Vehicle (LLRV) - 1969): >> >>     https://www.youtube.com/watch?v=cSlaYfxklm4 >> >>     Fred >> >>         Remark, contrary to the self-piloting(?) air taxies, the >> challenge for >> >>         self-driving cars is to see a car, or a group of cars, on the >> road >> >>         _without_ humans inside.  One did see drivers with hands off >> the wheel, >> >>         drivers on passenger seats (nobody on driver's seat), etc. >> >>         Alex >> >>         Le 23/01/2019 à 16:46, Templin (US), Fred L a écrit : >> >>             Hi, lately we have been talking quite a bit about flying >> cars and taxis in a >> >>             theoretical sense, but today Boeing has issued a public >> announcement >> >>             showing that they are one step closer to reality. Here is >> your air taxi for >> >>             the urban air mobility environment: >> >> >> https://www.yahoo.com/news/boeing-passenger-air-vehicle-prototype-111551329.html >> >> >>             Thanks - Fred >> >>             _______________________________________________ >> >>             its mailing list >> >>             its@ietf.org  >> >>             https://www.ietf.org/mailman/listinfo/its >> >>         _______________________________________________ >> >>         its mailing list >> >>         its@ietf.org  >> >>         https://www.ietf.org/mailman/listinfo/its >> > > _______________________________________________ > its mailing list > its@ietf.org > https://www.ietf.org/mailman/listinfo/its From nobody Sat Sep 19 09:50:49 2020 Return-Path: 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 CADCA3A0CBB for ; Sat, 19 Sep 2020 09:50:47 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.433 X-Spam-Level: X-Spam-Status: No, score=-1.433 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, MIME_QP_LONG_LINE=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_SOFTFAIL=0.665, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=syzygyengineering.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 q6qLJQMAl81o for ; Sat, 19 Sep 2020 09:50:46 -0700 (PDT) Received: from bird.elm.relay.mailchannels.net (bird.elm.relay.mailchannels.net [23.83.212.17]) (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 ED0313A0CB9 for ; Sat, 19 Sep 2020 09:50:45 -0700 (PDT) X-Sender-Id: a2hosting|x-authuser|ivancic@syzygyengineering.com Received: from relay.mailchannels.net (localhost [127.0.0.1]) by relay.mailchannels.net (Postfix) with ESMTP id 082807E0BE0; Sat, 19 Sep 2020 16:50:45 +0000 (UTC) Received: from mi3-ss16.a2hosting.com (100-96-22-112.trex.outbound.svc.cluster.local [100.96.22.112]) (Authenticated sender: a2hosting) by relay.mailchannels.net (Postfix) with ESMTPA id 533AD7E0E69; Sat, 19 Sep 2020 16:50:44 +0000 (UTC) X-Sender-Id: a2hosting|x-authuser|ivancic@syzygyengineering.com Received: from mi3-ss16.a2hosting.com (mi3-ss16.a2hosting.com [68.66.216.18]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384) by 0.0.0.0:2500 (trex/5.18.10); Sat, 19 Sep 2020 16:50:44 +0000 X-MC-Relay: Neutral X-MailChannels-SenderId: a2hosting|x-authuser|ivancic@syzygyengineering.com X-MailChannels-Auth-Id: a2hosting X-Well-Made-Daffy: 37d731b3153c7425_1600534244796_522655152 X-MC-Loop-Signature: 1600534244796:3181850065 X-MC-Ingress-Time: 1600534244796 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=syzygyengineering.com; s=default; h=Content-transfer-encoding:Content-type: Mime-version:In-Reply-To:References:Message-ID:To:From:Subject:Date:Sender: Reply-To:Cc:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help: List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=n3nBZbaNmhJslvPHSoeelI/5F3BL8TZZTsmaSFROjKM=; b=DrwWGN2oR8Gh1MKUIUp6f154/+ TmjzO/fHUItBVcMOT+bzOydzwnNryw3YVLTmOhyM42mS05FTGUTB38Dux9HlMi210rywnCZIeWvw0 DSfN0Nfs8kvzZOcRPGznXUGnvcDxUNax5F8SQKGDgj8eug2WqHr6naQq55knV0ay+lat29XpjodWJ DJgzNXcFCqvM3/QlpLiJG7TL+ZDcEwZ4hReXYUR5N4pf+hmTYdl6ykvNaiREDn5/fxkm7FKOvjpNr XG1w0z9Ul5rTNR3dJSptWZkpHTLs49TTQKvF4/FxFwTld64ExnXKLyMhkhE5pkebiF8xZ5OhYxfJE 1m3CNXyg==; Received: from d27-96-115-125.nap.wideopenwest.com ([96.27.125.115]:55029 helo=[192.168.0.2]) by mi3-ss16.a2hosting.com with esmtpsa (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.93) (envelope-from ) id 1kJg4R-0000nA-AD; Sat, 19 Sep 2020 12:50:43 -0400 User-Agent: Microsoft-MacOutlook/16.39.20071300 Date: Sat, 19 Sep 2020 12:50:40 -0400 From: William Ivancic To: Alexandre Petrescu , Message-ID: <73057803-AFD1-45A5-8C6F-690119C5AA60@syzygyengineering.com> Thread-Topic: [ipwave] Flying cars and taxi one step closer to reality References: <8a6a78ab29704f28a21eb483ae406910@boeing.com> <658b27943f9d4b1db2cd28d10fc7c7ff@boeing.com> <389ada57-38dd-25f1-6d52-a3dc9672c42c@gmail.com> In-Reply-To: Mime-version: 1.0 Content-type: text/plain; charset="UTF-8" Content-transfer-encoding: quoted-printable X-AuthUser: ivancic@syzygyengineering.com Archived-At: Subject: Re: [ipwave] Flying cars and taxi one step closer to reality 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 19 Sep 2020 16:50:48 -0000 The difficult part of Urban Air Mobility (UAM) is the air traffic control i= ssues. This is also a big problem that has to be worked out for drones to o= perate beyond visual line of sight - such as using LTE, 5G and other cellula= r technology for aircraft control. Will =EF=BB=BFOn 9/19/20, 12:32 PM, "its on behalf of Alexandre Petrescu" wrote: I learned about a new demo by Sky Drive Inc, model SD-03, on Toyota tes= t=20 field in Japan, shown on August 31st, 2020. https://www.lifo.gr/now/tech_science/294406/iaponia-epandromeno-iptamen= o-aytokinito-petakse-me-epityxia-pote-tha-vgei-stin-paragogi-vinteo (the content of the URL is in Greek) There is a person on-board who pilots the flight (he is not just=20 transported like in e.g. Ehang demo). The article says production is epxected by year 2023. Alex Le 22/10/2019 =C3=A0 16:01, Alexandre Petrescu a =C3=A9crit : > Fred, >=20 > I would like to know whether somebody came up with groups of such fly= ing=20 > taxis or VTOLs, like when they came up with 'platoon's of convoyed ca= rs=20 > on the ground? >=20 > Alex >=20 > Le 19/09/2019 =C3=A0 17:51, Templin (US), Fred L a =C3=A9crit : >> Alex, Urban Air Mobility is indeed inevitable and will be the vertic= al=20 >> component >> >> of an integrated 3D its landscape. Thanks for the pointer. >> >> Fred >> >> *From:*Alexandre Petrescu [mailto:alexandre.petrescu@gmail.com] >> *Sent:* Thursday, September 19, 2019 1:22 AM >> *To:* Templin (US), Fred L ; its@ietf.org >> *Subject:* Re: [ipwave] Flying cars and taxi one step closer to real= ity >> >> SEveral companies do more and more flying taxis, now safely with=20 >> people on board. It takes some courage, but it's a wider audience n= ow. >> >> 3. France 2 Telematin samedi 14 octobre "Futur du Transport Urbain",= =C3=A0=20 >> partir du 2:48:36 dela video=20 >> https://www.france.tv/france-2/telematin/1060857-telematin.html >> >> Le 24/01/2019 =C3=A0 16:34, Templin (US), Fred L a =C3=A9crit : >> >> Hi Alex, >> >> -----Original Message----- >> >> From: its [mailto:its-bounces@ietf.org] On Behalf Of Alexand= re=20 >> Petrescu >> >> Sent: Thursday, January 24, 2019 3:47 AM >> >> To:its@ietf.org >> >> Subject: Re: [ipwave] Flying cars and taxi one step closer t= o=20 >> reality >> >> Impressive, >> >> Thanks. >> >> The kind of thrill seeing these videos is similar to seeing=20 >> (manned) >> >> first plane vertical take-offs. >> >> Airbus also featured air taxi ambitious concepts (cartoons) = on=20 >> youtube >> >> since almost two years. >> >> A company named AKKA in Europe proposes a similar concept of= =20 >> more of a >> >> plane (horizontal take-off) which self-... flies. >> >> The Dubai air taxi did fly a year ago, but there was no huma= n=20 >> inside, so >> >> one legitimately wonders whether it could actually carry tha= t=20 >> much weight. >> >> The new thing about the boeing video is that we see larger=20 >> propellers >> >> and a dummy body inside (hopefully weighted). It seems much= =20 >> closer to >> >> implementations. Impressive. >> >> The next step would be to see a human take responsibility of= =20 >> sitting on >> >> the drone while lifting a few meters above ground. Like in=20 >> what they >> >> did with first elevator in NYC, first man in first plane, br= idge >> >> engineer first walk on bridge, agency director first liftoff= =20 >> towards >> >> first man in space, etc. Until then one still doubts :-) >> >> Already been done, and a long time ago (Lunar Landing Research >> >> Vehicle (LLRV) - 1969): >> >> https://www.youtube.com/watch?v=3DcSlaYfxklm4 >> >> Fred >> >> Remark, contrary to the self-piloting(?) air taxies, the=20 >> challenge for >> >> self-driving cars is to see a car, or a group of cars, on th= e=20 >> road >> >> _without_ humans inside. One did see drivers with hands off= =20 >> the wheel, >> >> drivers on passenger seats (nobody on driver's seat), etc. >> >> Alex >> >> Le 23/01/2019 =C3=A0 16:46, Templin (US), Fred L a =C3=A9crit : >> >> Hi, lately we have been talking quite a bit about flying= =20 >> cars and taxis in a >> >> theoretical sense, but today Boeing has issued a public=20 >> announcement >> >> showing that they are one step closer to reality. Here i= s=20 >> your air taxi for >> >> the urban air mobility environment: >> >> =20 >> https://www.yahoo.com/news/boeing-passenger-air-vehicle-prototype-11= 1551329.html=20 >> >> >> Thanks - Fred >> >> _______________________________________________ >> >> its mailing list >> >> its@ietf.org >> >> https://www.ietf.org/mailman/listinfo/its >> >> _______________________________________________ >> >> its mailing list >> >> its@ietf.org >> >> https://www.ietf.org/mailman/listinfo/its >> >=20 > _______________________________________________ > its mailing list > its@ietf.org > https://www.ietf.org/mailman/listinfo/its _______________________________________________ its mailing list its@ietf.org https://www.ietf.org/mailman/listinfo/its From nobody Tue Sep 29 05:19:44 2020 Return-Path: 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 0005D3A05AC for ; Tue, 29 Sep 2020 05:19:43 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 0.458 X-Spam-Level: X-Spam-Status: No, score=0.458 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FORGED_GMAIL_RCVD=1, FREEMAIL_FROM=0.001, NICE_REPLY_A=-0.213, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_SOFTFAIL=0.665, URIBL_BLOCKED=0.001] autolearn=no 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 4WDe_h0t-ko3 for ; Tue, 29 Sep 2020 05:19:42 -0700 (PDT) Received: from cirse-smtp-out.extra.cea.fr (cirse-smtp-out.extra.cea.fr [132.167.192.148]) (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 4021E3A0489 for ; Tue, 29 Sep 2020 05:19:42 -0700 (PDT) Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by cirse-sys.extra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id 08TCJcY4010431 for ; Tue, 29 Sep 2020 14:19:38 +0200 Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 44421205F02 for ; Tue, 29 Sep 2020 14:19:38 +0200 (CEST) Received: from muguet1-smtp-out.intra.cea.fr (muguet1-smtp-out.intra.cea.fr [132.166.192.12]) by pisaure.intra.cea.fr (Postfix) with ESMTP id 37C46205DF8 for ; Tue, 29 Sep 2020 14:19:38 +0200 (CEST) Received: from [10.8.35.150] (is154594.intra.cea.fr [10.8.35.150]) by muguet1-sys.intra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id 08TCJceq030601 for ; Tue, 29 Sep 2020 14:19:38 +0200 To: its@ietf.org References: <92850021-914f-ab6a-f8d2-ab793179fa1b@gmail.com> <00d601d5b4ee$01cc9ae0$0565d0a0$@eurecom.fr> <47f48fca-07b9-5657-4cb5-54cc5d63d2e3@gmail.com> <7664b128-91b7-8fef-1e13-b681b45b1958@gmail.com> <61f9d6f6-1e37-6e15-3a48-48e7047f0fe1@gmail.com> <7f2e764a-8d75-a3a8-cd4e-a4406dd8e321@gmail.com> <038fea3b-cdd3-dbe3-04f9-fbe873661cf1@gmail.com> <0e29e730-e62a-f864-ad10-81f5e524bf33@gmail.com> From: Alexandre Petrescu Message-ID: Date: Tue, 29 Sep 2020 14:19:37 +0200 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.2.2 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: fr Content-Transfer-Encoding: 8bit Archived-At: Subject: Re: [ipwave] Commenting on the FCC plan 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Sep 2020 12:19:44 -0000 For information, today some 5G frequencies go on auction in France. The bands are in the 3.49-3.8GHz area. The price starts at 350MEur for a 50MHz, then down. I suspect that, this being an 'auction', it means the price will go up too. There is no talk of 4.9GHz bands for 5G. This means probably the FCC plan to carve 5G space into 4.9GHz V2X bands does not affect the France plans of 5G. Another remarkable point is that the 5G bands auction comes with a requirement for IPv6 compatibility, which is good for IPv6 in general but does not affect V2X either ("Par ailleurs, pour accélérer la transition vers le protocole de routage IPv6, l'Arcep prévoit une obligation pour rendre les réseaux mobiles compatibles avec celui-ci.", fr.) Alex Le 10/07/2020 à 17:37, Alexandre Petrescu a écrit : > This IPv6 restriction doubt aside, has now FCC allocated 5.9GHz channels > to non-802.11 technologies? > > Le 10/07/2020 à 16:33, fygsimon@gmail.com a écrit : >> IPv6 was never restricted on the DSRC Control Channel by the FCC.  I >>  believe this was a restriction mandate by IEEE 1609.x standard(s). > > I can only hope by now that IEEE 1609.x drafts do say "RFC 8691". > >> The applicable US Codes of Federal Regulations are: >> >> FCC 47 90.377 for RSU >> >> FCC 47 95.325, 95.359, 95.3159, 95.3163, and 95.3167 which replace >> 95.1511 since 2017. > > These should say "RFC 8691" to clarify any potential confusion. > > Alex > >> >> Have any questions, let me know. >> >> Francois Simon >> >> Sent from Mail for >> Windows 10 >> >> *From: *Abdussalam Baryun *Sent: >> *Friday, July 10, 2020 9:31 AM *To: *Alexandre Petrescu >> ; its >> *Subject: *Re: [ipwave] Commenting on the FCC plan >> >> thanks Alex, >> >> On Fri, Jul 10, 2020 at 2:43 PM Alexandre Petrescu >> > >> wrote: >> >> Hello, >> >> I would like to know wheher FCC advanced well while seeking to >> promote innovation in the 5.9GHz band? >> >> In particular, is now IPv6 allowed to run on the control channel >> 5895-5905MHz on 802.11 in OCB mode? >> >> I think it will be licensed or on demand. >> >> The URL to the FCC document stating that seeking of promotion of >> innovation is this, but I cant figure out a conclusion of it(?) >> https://www.fcc.gov/document/fcc-seeks-promote-innovation-59-ghz-band-0 >> >>  Best regards >> >> AB >> > > _______________________________________________ > its mailing list > its@ietf.org > https://www.ietf.org/mailman/listinfo/its