Re: [v6ops] IPv6 over 802.11p - no modifications required

Brian E Carpenter <brian.e.carpenter@gmail.com> Mon, 02 December 2013 18:57 UTC

Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B7CE61AD8CD for <v6ops@ietfa.amsl.com>; Mon, 2 Dec 2013 10:57:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
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 T2pHSud7R4Wh for <v6ops@ietfa.amsl.com>; Mon, 2 Dec 2013 10:57:53 -0800 (PST)
Received: from mail-pb0-x22d.google.com (mail-pb0-x22d.google.com [IPv6:2607:f8b0:400e:c01::22d]) by ietfa.amsl.com (Postfix) with ESMTP id 636701AC404 for <v6ops@ietf.org>; Mon, 2 Dec 2013 10:57:53 -0800 (PST)
Received: by mail-pb0-f45.google.com with SMTP id rp16so19529379pbb.4 for <v6ops@ietf.org>; Mon, 02 Dec 2013 10:57:51 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=sgr2I9RLybtUN05Q5XVW4DPc/z0+9do2eCKRWn5nvac=; b=US3EcTR/uobsmj3AhasN8IJGyAnVhomi96O4bXRAGD2GmO0Ry7RbyqVW9Ujr6MU0Yb MKQYbfCpnljmVQ3RiF2ftUgJ+KqHPdQJpaR0KO0iQ8OvAMwsuQcJkm1cZpyPP4uLYW5R s484B96U2uZVRLvtAZLuJBOk5T7b1zXFE+aRZSUrTQwRtLroqpUVBI0GQDwDyQv4RDi8 o4HgI0ZBv3E0uM7qdCdsWdspjOzV82S/9pB3cYqlILZNtWWSWUVvQd1xYMGAX5HwY2E6 W61d+4EZht7q+WS0A9kSJ8AVDN8P7vzEYPDcbvRTMxxszK0MPGxMiY/mLqGkLPE874bS u+CA==
X-Received: by 10.67.1.101 with SMTP id bf5mr68614154pad.50.1386010671151; Mon, 02 Dec 2013 10:57:51 -0800 (PST)
Received: from [192.168.178.20] (226.199.69.111.dynamic.snap.net.nz. [111.69.199.226]) by mx.google.com with ESMTPSA id xn12sm91409469pac.12.2013.12.02.10.57.49 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 02 Dec 2013 10:57:50 -0800 (PST)
Message-ID: <529CD82A.4010506@gmail.com>
Date: Tue, 03 Dec 2013 07:57:46 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Alexandru Petrescu <alexandru.petrescu@gmail.com>
References: <529C6A6D.6070307@gmail.com>
In-Reply-To: <529C6A6D.6070307@gmail.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Cc: "v6ops@ietf.org" <v6ops@ietf.org>
Subject: Re: [v6ops] IPv6 over 802.11p - no modifications required
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 02 Dec 2013 18:57:54 -0000

Hi

1. Surely this should be a 6man document, not v6ops?

2. "5.5. Stateless Autoconfiguration


   The Interface Identifier for an 802.11p interface is formed using the
   same rules as the Interface Identifier for an Ethernet interface;
   this is described in section 4 of [RFC2464]."

Given the discussion of deprecating EUI-64, I think this should be:

   "The Interface Identifier for an 802.11p interface may be formed..."

3. I notice that you cite the RFC 2119 terminology but the draft doesn't
actually use it. If you don't use it, please don't cite it.

Regards
   Brian Carpenter

On 03/12/2013 00:09, Alexandru Petrescu wrote:
> draft-petrescu-ipv6-over-80211p-01.txt
> 
> Hello participants to v6ops,
> 
> Running IPv6 over 802.11p requires no modifications to the protocol: it
> runs just as IPv6 over Ethernet does - same 0x86DD Ethertype, same
> recommended minimal MTU, same formation of the Interface ID, ...
> 
> However, in some operational environments, some tweaks may be necessary
> due to specificities of the link (e.g. OCB - outside the context of a
> BSS id): frequent Router Advertisements to support handover of
> high-speed vehicles through distanced Road-Side Units, and IP security
> messages because the link layer has no security features.
> 
> This is what this draft describes:
> 
> "Transmission of IPv6 Packets over IEEE 802.11p Networks"
> A. Petrescu, R. Kuntz, P. Pfister, N. Benamar
> http://tools.ietf.org/html/draft-petrescu-ipv6-over-80211p-01
> 
> What do you think?
> 
> Alex
> 
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops
>