Re: [ipwave] Should the IPWAVE WG adopt draft-jeong-ipwave-vehicular-networking-survey?
Russ Housley <housley@vigilsec.com> Fri, 23 June 2017 18:34 UTC
Return-Path: <housley@vigilsec.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 3E53D1286B2 for <its@ietfa.amsl.com>; Fri, 23 Jun 2017 11:34:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 taiHo0CUj6tv for <its@ietfa.amsl.com>; Fri, 23 Jun 2017 11:34:06 -0700 (PDT)
Received: from mail.smeinc.net (mail.smeinc.net [209.135.209.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4900F12700F for <its@ietf.org>; Fri, 23 Jun 2017 11:34:06 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mail.smeinc.net (Postfix) with ESMTP id B403A300466 for <its@ietf.org>; Fri, 23 Jun 2017 14:34:05 -0400 (EDT)
X-Virus-Scanned: amavisd-new at mail.smeinc.net
Received: from mail.smeinc.net ([127.0.0.1]) by localhost (mail.smeinc.net [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id hW6Ot457wlfj for <its@ietf.org>; Fri, 23 Jun 2017 14:34:04 -0400 (EDT)
Received: from a860b60074bd.home (pool-108-45-101-150.washdc.fios.verizon.net [108.45.101.150]) by mail.smeinc.net (Postfix) with ESMTPSA id 851D030009D for <its@ietf.org>; Fri, 23 Jun 2017 14:34:04 -0400 (EDT)
From: Russ Housley <housley@vigilsec.com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Date: Fri, 23 Jun 2017 14:34:03 -0400
References: <CA50A382-F591-4A33-BAF9-1903E107BE02@vigilsec.com>
To: its <its@ietf.org>
In-Reply-To: <CA50A382-F591-4A33-BAF9-1903E107BE02@vigilsec.com>
Message-Id: <FCE87AE6-AB1A-47FF-B7E5-B4A0EEDB787F@vigilsec.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/its/dfcrhcTEKS-Npax-6e19uOIQIMo>
Subject: Re: [ipwave] Should the IPWAVE WG adopt draft-jeong-ipwave-vehicular-networking-survey?
X-BeenThere: its@ietf.org
X-Mailman-Version: 2.1.22
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: Fri, 23 Jun 2017 18:34:08 -0000
We have support for adoption of this Internet-Draft; however, the discussion has raised some topics that need to be worked on. The current I-D says: This Internet-Draft is submitted to IETF in full conformance with the provisions of BCP 78 and BCP 79. So, I ask that the authors ensure that any needed IPR statements are posted prior to the posting of a draft-ietf-ipwave-vehicular-networking-survey-00. Russ & Carlos > On Jun 6, 2017, at 9:59 AM, Russ Housley <housley@vigilsec.com> wrote: > > The IPWAVE WG charter calls for the group to publish an Informational document: > > This group will work on an informational document > that will explain the state of the art in the field and describe > the use cases that will use IPv6 in order to focus the work of > the group. > > Should the IPWAVE WG adopt draft-jeong-ipwave-vehicular-networking-survey > as the starting point for this deliverable? > > See https://datatracker.ietf.org/doc/draft-jeong-ipwave-vehicular-networking-survey/ > > Russ
- [ipwave] Should the IPWAVE WG adopt draft-jeong-i… Russ Housley
- Re: [ipwave] Should the IPWAVE WG adopt draft-jeo… Alexandre Petrescu
- Re: [ipwave] Should the IPWAVE WG adopt draft-jeo… Nabil Benamar
- Re: [ipwave] Should the IPWAVE WG adopt draft-jeo… José Santa Lozano
- Re: [ipwave] Should the IPWAVE WG adopt draft-jeo… Carlos Jesús Bernardos Cano
- Re: [ipwave] Should the IPWAVE WG adopt draft-jeo… Dirk.von-Hugo
- Re: [ipwave] Should the IPWAVE WG adopt draft-jeo… Rex Buddenberg
- Re: [ipwave] Should the IPWAVE WG adopt draft-jeo… Carlos Jesús Bernardos Cano
- Re: [ipwave] Should the IPWAVE WG adopt draft-jeo… Mr. Jaehoon Paul Jeong
- Re: [ipwave] Should the IPWAVE WG adopt draft-jeo… Rex Buddenberg
- Re: [ipwave] Should the IPWAVE WG adopt draft-jeo… Chris Shen
- Re: [ipwave] Should the IPWAVE WG adopt draft-jeo… Mr. Jaehoon Paul Jeong
- Re: [ipwave] Should the IPWAVE WG adopt draft-jeo… Tony Li
- Re: [ipwave] Should the IPWAVE WG adopt draft-jeo… Rex Buddenberg
- Re: [ipwave] Should the IPWAVE WG adopt draft-jeo… tony.li
- Re: [ipwave] Should the IPWAVE WG adopt draft-jeo… Rex Buddenberg
- Re: [ipwave] Should the IPWAVE WG adopt draft-jeo… Russ Housley
- Re: [ipwave] Should the IPWAVE WG adopt draft-jeo… Abdussalam Baryun