Re: [ipwave] Expertise on ND problems on OCB

Charlie Perkins <charles.perkins@earthlink.net> Fri, 26 April 2019 17:31 UTC

Return-Path: <charles.perkins@earthlink.net>
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 D95C8120472; Fri, 26 Apr 2019 10:31:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, 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=earthlink.net; domainkeys=pass (2048-bit key) header.from=charles.perkins@earthlink.net header.d=earthlink.net
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 XQYNZcLRzKR5; Fri, 26 Apr 2019 10:31:07 -0700 (PDT)
Received: from elasmtp-dupuy.atl.sa.earthlink.net (elasmtp-dupuy.atl.sa.earthlink.net [209.86.89.62]) (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 8F1D012046F; Fri, 26 Apr 2019 10:31:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=earthlink.net; s=dk12062016; t=1556299862; bh=k6wNpzEzaK3i0+XY9A0qaQlrLVEHRVgy8ktF ZNHw7Q0=; h=Received:Subject:To:Cc:References:From:Message-ID:Date: User-Agent:MIME-Version:In-Reply-To:Content-Type: Content-Transfer-Encoding:Content-Language:X-ELNK-Trace: X-Originating-IP; b=Qcpa7p8e8IRbrtiK3cK0t+1KDPTi4Fp9DyGVycZOLRpdzW rzNi6Zr4lss4LcL6AS0Slyk/WTvAqu6zyYsERyE7mQe3MSfwhxxVqTw5PfGKqVmB+MT 93w+u1TMkIm786fwzPPmPxSHOcBs8n1l1wSF2K2gmhw7T/3W2jKgsIIs2BwQp0yabl5 L16g36UtK4fAzOIQ8y/GRrBBBhQMmnLTCyJf0gYHgpsUxBsr1BY+kPW/VyCQd2Ul2Aq 1DHqNACtswQF+5z2NtJSHjQdjAt51/GKCVcNKqtGn7Wt3mdixzmXxPx9L25QHDiemVH R8w0TdnJso7aQbmEHr3f9T7o6TPA==
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk12062016; d=earthlink.net; b=oumVpJoMNEHo60UxHyN3puXvL5YWTh0PJ6s83hmHFIod/JPWfhk/bkn7D2EPhR7hsv1Q05d7a0pgCJGgDUStCxiib9+Y4v+YAiKnZ486I4HyHkfaXkqEeGARepkmES+2hwx/BO/e2RlzOc+h4Bp3BfR9ZYNaGEbTCv7DAcG1RJfjdN51PpPbIDafTUjOMttfdAnbPTNl/RwaIjQcz4fFGOukWiP32LCvdUGEU0eF9b67wBLU2jo1wmpGKnZWwLlAGaWShRu4/UpQwh11GLXMTQI9iY5oUSZfSUFlKsLJjnufYYWcv8Zn7FrjZMErDgKXiDBLmshFjsm6ZoEbl6u1fA==; h=Received:Subject:To:Cc:References:From:Message-ID:Date:User-Agent:MIME-Version:In-Reply-To:Content-Type:Content-Transfer-Encoding:Content-Language:X-ELNK-Trace:X-Originating-IP;
Received: from [99.51.72.196] (helo=[192.168.1.82]) by elasmtp-dupuy.atl.sa.earthlink.net with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4) (envelope-from <charles.perkins@earthlink.net>) id 1hK4gf-000FnC-AX; Fri, 26 Apr 2019 13:31:01 -0400
To: "Sri Gundavelli (sgundave)" <sgundave@cisco.com>, "draft-ietf-ipwave-ipv6-over-80211ocb.all@ietf.org" <draft-ietf-ipwave-ipv6-over-80211ocb.all@ietf.org>
Cc: "its@ietf.org" <its@ietf.org>
References: <155169869045.5118.3508360720339540639@ietfa.amsl.com> <a8aad636-069c-4451-dbf1-72c1db2204ef@gmail.com> <CAD8vqFfx_FVi5NobrR1p6xEKjkSNa1_ZejgrEs3JPDHJQoxD7A@mail.gmail.com> <MN2PR11MB356570FDBC5798F155DDEE25D82C0@MN2PR11MB3565.namprd11.prod.outlook.com> <CAMugd_Xce5cWLtVB4DbR1ZEaFbdfiRpXre9oq61ukRC+n+3cZw@mail.gmail.com> <D8D5F0B7.2F2BB8%sgundave@cisco.com> <D8D5F510.2F2BC8%sgundave@cisco.com> <3e716b4b-8236-0488-309c-7cd3a54db7b5@gmail.com> <D8D7B1E7.2F2CA2%sgundave@cisco.com> <CAD8vqFfSGKhw_ou3VB98C8r1gq=4WD8+f8C5P53C46k-0V+XuA@mail.gmail.com> <66e7c810-45a5-5244-59dc-4b764b6fb346@gmail.com> <1a6599ee-88f9-42d9-a208-918ba6711612@gmail.com> <11645738-6f95-82e5-48f1-ebc3ce54423e@gmail.com> <6aaea808-6013-cd73-c894-c29fd8c98ac8@gmail.com> <72f60b2f-0a3a-8d60-f6de-09c058913c33@earthlink.net> <CADnDZ8-nBqJLibwumn_p8AtmZ9P2wPgfMmTUme4-DPxCO5jRZg@mail.gmail.com> <650B0FE9-2C26-40C5-8916-B190F3D54831@tzi.org> <D8E87D73.2F510F%sgundave@cisco.com>
From: Charlie Perkins <charles.perkins@earthlink.net>
Message-ID: <934fc172-9c11-2316-4a4a-265749ad486a@earthlink.net>
Date: Fri, 26 Apr 2019 10:30:59 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1
MIME-Version: 1.0
In-Reply-To: <D8E87D73.2F510F%sgundave@cisco.com>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 8bit
Content-Language: en-US
X-ELNK-Trace: 137d7d78656ed6919973fd6a8f21c4f2d780f4a490ca6956846b590522b13c95c1132e8a99fdc736e5d126e3ac8a44e8350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 99.51.72.196
Archived-At: <https://mailarchive.ietf.org/arch/msg/its/43RNGh3ALs9YOAIWaHD0NpgXFEA>
Subject: Re: [ipwave] Expertise on ND problems on OCB
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: Fri, 26 Apr 2019 17:31:10 -0000

Hello Sri,

Forget about RFC 8505.

What about a solution resident on relatively fixed infrastructure that 
performs proxy ND services for vehicles in the neighborhood?

To me that sounds like an attractive sort of solution.  It could relieve 
the vehicles of their requirement to carry out RFC 4861 on-link ND 
protocol operations.   Moreover, it seems to me that unicast might be 
preferable to multicast in vehicular ND protocols, because of the issues 
outlined in previous emails and drafts.  Do you disagree?

We shouldn't get stuck talking about low power when that issue isn't 
germane to the discussion.

Regards,
Charlie P.

PS. I hope it's O.K. if I trimmed the long list of respondents. Does 
every message need to go to ietf@ietf.org too??


On 4/26/2019 9:31 AM, Sri Gundavelli (sgundave) wrote:
> I am sure you are convinced, but myself and many others in the WG have a
> hard time seeing  RFC 8505 applicability to vehicular environments.  There
> may be elements from RFC 8505, and many other specs, may be leveraged, but
> this characterization of RFC 8505 as the ND solution is not convincing to
> me, or to most people in the group (IMO); specially for a spec designed in
> 6lo for low-power devices, and with the problem statement documented in
> RFC 4919 not identifying a single vehicular property. You may have to
> start revising RFC 4919 to change the scope of 6lo work.
>
>
> Sri
>
>
>
>
> On 4/25/19, 12:42 PM, "its on behalf of Carsten Bormann"
> <its-bounces@ietf.org on behalf of cabo@tzi.org> wrote:
>
>>>> 	€ RFC 8505 isn't just about low power.
>>> The titles says that, so the authors said that and including the IETF
>>> WG that published and examined it under such use cases
>> Actually, it doesn¹t.
>>
>> The title is
>>
>> Registration Extensions for IPv6 over
>> 6LoWPAN Neighbor Discovery
>>
>> because 6LoWPAN Neighbor Discovery was invented for 6LoWPAN before we
>> started applying it to the entirety of 6Lo.
>>
>> The RFC editor guidelines caused this title to be expanded to:
>>
>> Registration Extensions for IPv6 over
>> Low-Power Wireless Personal Area Network (6LoWPAN) Neighbor Discovery
>>
>> which is indeed the expansion of ³6LoWPAN², but does not help at all ‹ it
>> just muddies the waters by polluting the title with terms that are no
>> longer relevant to the document at hand.
>>
>> (I¹m not going to go into the other parts of the current discussion; I
>> have no idea how something like OCB can be discussed without
>> acknowledging the hidden terminal problem, a.k.a. non-transitive
>> connectivity, so it seems to me I won't have much to contribute.)
>>
>> Grüße, Carsten
>>
>> _______________________________________________
>> its mailing list
>> its@ietf.org
>> https://www.ietf.org/mailman/listinfo/its
>