From owner-freebsd-wireless@FreeBSD.ORG  Sun Jun 30 21:14:31 2013
Return-Path: <owner-freebsd-wireless@FreeBSD.ORG>
Delivered-To: freebsd-wireless@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by hub.freebsd.org (Postfix) with ESMTP id 1BE4FAF2;
 Sun, 30 Jun 2013 21:14:31 +0000 (UTC) (envelope-from lev@FreeBSD.org)
Received: from onlyone.friendlyhosting.spb.ru (onlyone.friendlyhosting.spb.ru
 [46.4.40.135]) by mx1.freebsd.org (Postfix) with ESMTP id CCB511C45;
 Sun, 30 Jun 2013 21:14:30 +0000 (UTC)
Received: from lion.home.serebryakov.spb.ru (unknown
 [IPv6:2001:470:923f:1:4576:f46b:6d13:91c5])
 (Authenticated sender: lev@serebryakov.spb.ru)
 by onlyone.friendlyhosting.spb.ru (Postfix) with ESMTPSA id 9120D4AC58;
 Mon,  1 Jul 2013 01:14:28 +0400 (MSK)
Date: Mon, 1 Jul 2013 01:14:16 +0400
From: Lev Serebryakov <lev@FreeBSD.org>
X-Priority: 3 (Normal)
Message-ID: <1032749777.20130701011416@serebryakov.spb.ru>
To: Adrian Chadd <adrian@freebsd.org>
Subject: Re: CFT: wpa_supplicant/hostapd import patch
In-Reply-To: <CAJ-VmonB3PP4KbgEJ7POUbNp8k2_X+9UoS09=-rS0N=nVE5YtA@mail.gmail.com>
References: <7671255B-5582-428A-8ADC-3DF7AA32C772@FreeBSD.org>
 <8819701.20130630194938@serebryakov.spb.ru>
 <A3A05313-D783-4633-BD60-9E5CA1B7F95B@FreeBSD.org>
 <EF43F13C-9803-47F2-8A2A-FCBCC9BBED4F@FreeBSD.org>
 <1415556931.20130701000811@serebryakov.spb.ru>
 <DCDC6F3A-03AF-4DCB-A66C-BD9DC832B12D@FreeBSD.org>
 <638557210.20130701001136@serebryakov.spb.ru>
 <FD107753-1E4D-43AC-B8E0-06D33A10D196@FreeBSD.org>
 <1342388755.20130701001505@serebryakov.spb.ru>
 <B1B0EA44-1D91-4DE8-AC40-A22176496DD8@FreeBSD.org>
 <157797947.20130701002516@serebryakov.spb.ru>
 <775B2027-C5FC-4433-9E7C-B608DA937314@FreeBSD.org>
 <CAJ-Vmo=MHi1B8BpjdaE7c1qmOOUScpi63bcdQfZ5YORuazrJAA@mail.gmail.com>
 <CAJ-Vmo=Dc9ye40TOYJebm3t9fvpwxfMGOR=BLGQi3_CRzzN00w@mail.gmail.com>
 <1848916453.20130701004258@serebryakov.spb.ru>
 <CAJ-VmomRWZim0fiSJ5yW34ZfpMR5Km=AuKexjMmyvwnW=YhN3w@mail.gmail.com>
 <CAJ-VmonfUsj+EO9r=HdPbWVYM5XjVtD6xqeQBAhm4FSQa2nMmA@mail.gmail.com>
 <318287511.20130701005606@serebryakov.spb.ru> <CAJ-VmonB3PP4KbgEJ7POUbNp8k2_
 X+9UoS09=-rS0N=nVE5YtA@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Cc: "freebsd-wireless@freebsd.org" <freebsd-wireless@freebsd.org>
X-BeenThere: freebsd-wireless@freebsd.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: "Discussions of 802.11 stack,
 tools device driver development." <freebsd-wireless.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-wireless>, 
 <mailto:freebsd-wireless-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-wireless>
List-Post: <mailto:freebsd-wireless@freebsd.org>
List-Help: <mailto:freebsd-wireless-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-wireless>, 
 <mailto:freebsd-wireless-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 30 Jun 2013 21:14:31 -0000

Hello, Adrian.
You wrote 1 =D0=B8=D1=8E=D0=BB=D1=8F 2013 =D0=B3., 1:00:49:

AC> Certification isn't our problem. That's a manufacturer problem.

AC> _THEY_ have to certify the device anyway. Regardless of whether we
AC> have the stack certified.
  I don't know WiFi Alliance rules, but when I participated in project,
  which included custom MasterCard/Visa terminal, PCI/DSS certification was
  much more simple and more straightforward in case, when device was based
  on certified platform (Certified ARM CPU + certified crypto library
  specific to this ARM chip). A whole bunch of certification steps was
  skipped by showing that we use certified platform. So, it was competitive
  advantage of provider of this platform :)

  But, may be, it is not a case in case of WiFi certification, I don't know.
  And anyway, we are far from this now :) It is too early to worry about
  certification, you are right.


--=20
// Black Lion AKA Lev Serebryakov <lev@FreeBSD.org>