Re: [ipwave] 802.11p minor textual issue

Russ Housley <housley@vigilsec.com> Thu, 18 May 2017 15:19 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 D98DD126CBF for <its@ietfa.amsl.com>; Thu, 18 May 2017 08:19:54 -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, HTML_MESSAGE=0.001, 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 06GXJsllv7kU for <its@ietfa.amsl.com>; Thu, 18 May 2017 08:19:52 -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 09B47129C3E for <its@ietf.org>; Thu, 18 May 2017 08:14:00 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mail.smeinc.net (Postfix) with ESMTP id 6EE45300537 for <its@ietf.org>; Thu, 18 May 2017 11:13:59 -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 73OFnldHP32j for <its@ietf.org>; Thu, 18 May 2017 11:13:57 -0400 (EDT)
Received: from [5.5.33.143] (vpn.snozzages.com [204.42.252.17]) by mail.smeinc.net (Postfix) with ESMTPSA id DC758300265; Thu, 18 May 2017 11:13:56 -0400 (EDT)
From: Russ Housley <housley@vigilsec.com>
Message-Id: <B16F201B-B72C-4EFB-8820-967BBA6C0637@vigilsec.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_EF68C48B-9884-4C01-96CA-5FB55BB07D7C"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Date: Thu, 18 May 2017 11:13:58 -0400
In-Reply-To: <CAP6QOWTEuHxAvd+wmD7VyR9+UzpWhkpH4gBz62Vs7pc-Gct8wA@mail.gmail.com>
Cc: "its@ietf.org" <its@ietf.org>
To: John Kenney <jkenney@us.toyota-itc.com>
References: <b7d0f246-da90-ac56-db69-40e9e929900d@gmail.com> <A0A28D59-30CC-44FD-90FB-9030EDB8E794@vigilsec.com> <CAP6QOWTEuHxAvd+wmD7VyR9+UzpWhkpH4gBz62Vs7pc-Gct8wA@mail.gmail.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/its/jsaNM7xa22d490m4n8V1SqQO1jo>
Subject: Re: [ipwave] 802.11p minor textual issue
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: Thu, 18 May 2017 15:19:55 -0000

Thanks.  For providing this quote.  I think it makes searching difficult for the reader, but we should follow IEEE-SA guidelines.

Russ


> On May 18, 2017, at 11:09 AM, John Kenney <jkenney@us.toyota-itc.com> wrote:
> 
> FYI, when the IEEE 1609 WG recently prepared a document that cited our standards, we were told by IEEE to do it this way:
> 
> The NPRM references IEEE standards that have been superseded by these more recently published IEEE standards: IEEE Std 802.11TM-2016, IEEE Std 1609.2 TM -2016, IEEE Std 1609.3 TM -2016, IEEE Std 1609.4 TM -2016, and IEEE Std 1609.12 TM -2016
> 
> Here is a quote from the IEEE-SA Standards Style Manual <https://development.standards.ieee.org/myproject/Public/mytools/draft/styleman.pdf> (section 7):
> "IEEE designations are trademarks of the IEEE and shall be identified as trademarks (® or ™, as appropriate) at first citation of each designation in the frontmatter and in the body of the draft."
> 
> So, if the text quoted by Alex is the first citation in the ID, I believe it would be correct to include TM not only for the 11p amendment, but also for 802.11-2007 since it is a different publication.
> 
> Best Regards,
> John
> 
> 
> 
> On Thu, May 18, 2017 at 6:38 AM, Russ Housley <housley@vigilsec.com <mailto:housley@vigilsec.com>> wrote:
> 
>> On May 18, 2017, at 5:39 AM, Alexandre Petrescu <alexandre.petrescu@gmail.com <mailto:alexandre.petrescu@gmail.com>> wrote:
>> 
>> OLD:
>>> The link 802.11 OCB was specified in IEEE Std 802.11p(TM)-2010
>>> [ieee802.11p-2010] as an amendment to the 802.11 specifications
>> 
>> It was suggested that the "802.11 specifications" are in fact "IEEE Std
>> 802.11-2007".  As such the resolution is:
>> 
>> NEW:
>>> The link 802.11 OCB was specified in IEEE Std 802.11p(TM)-2010
>>> [ieee802.11p-2010] as an amendment to IEEE Std 802.11-2007
>> 
>> End issue.
> 
> Alex:
> 
> I do not believe that the "(TM)" should appear in the name.  I suggest IEEE Std 802.11p-2010.
> 
> Also, it might help people locate the specification if we tell people that OCB was first specified in IEEE Std 802.11p-2010 as an amendment to IEEE Std 802.11-2007, and then it was incorporated into the base standard in …
> 
> Russ
> 
> 
> _______________________________________________
> its mailing list
> its@ietf.org <mailto:its@ietf.org>
> https://www.ietf.org/mailman/listinfo/its <https://www.ietf.org/mailman/listinfo/its>
> 
> 
> 
> 
> -- 
> John Kenney
> Director and Principal Researcher
> Toyota InfoTechnology Center, USA
> 465 Bernardo Avenue
> Mountain View, CA 94043
> Tel: 650-694-4160. Mobile: 650-224-6644