From owner-freebsd-wireless@freebsd.org Sun Aug 9 16:47:39 2020 Return-Path: Delivered-To: freebsd-wireless@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 979583B904B for ; Sun, 9 Aug 2020 16:47:39 +0000 (UTC) (envelope-from notjanedeere@gmail.com) Received: from mail-qt1-x830.google.com (mail-qt1-x830.google.com [IPv6:2607:f8b0:4864:20::830]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4BPlQ260YZz4CQm for ; Sun, 9 Aug 2020 16:47:38 +0000 (UTC) (envelope-from notjanedeere@gmail.com) Received: by mail-qt1-x830.google.com with SMTP id w9so5075881qts.6 for ; Sun, 09 Aug 2020 09:47:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding:content-language; bh=56dfcxnZk56Ey3DrTBlolvJuN54UqdqStlUTiBYEdzI=; b=LZrMcciPPlKDa2HOeAFqNm9EcysAEzPWcQKcyEmSbq3KKXZe9VcwMjwdO5kCNegB7W CidA2Aue1wrDPnupxJpkrMjNZjbYhdRMFx30uvVNWcmVzBTrDMHiN70YaFPugm947pEb LKyeICeNhcLCZtbr6pOepsD9MRncL54ZDCw2clUntGSF6rhx0TXnks5XRTQUWnNQBleb DOaMJQGKA8EXW5Z5LhwRZpENXdwGDIb3i+MZJK7DwhK3zKxWw/EFvRONkeVQV52VMTae x+cOq40CKf0ntA4IMDVTIwpIrLF2VKSqWtOU7JhQCntuueaUxRpr8Bn3E+bVCbQDVCpj 3HLw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=56dfcxnZk56Ey3DrTBlolvJuN54UqdqStlUTiBYEdzI=; b=cOCIYF/IdQY6q//pkFLER35vnhPANQUiug2JeyC/tWYP+JCmKkBsBntNNpwEpN3Ym1 k3bWT0RM5a66rop4lBNDze/S8x07/Lsi/VfdfaBYRCcIZ9Rv/DLBOWC+w1hjLuqvs0mk A6OK0Agp2tEWqUA7BwYC919mEwHgr+E7zVXdAtr56QyRUvfj3ZKEaGTM597I1DJvR/Pw M7VvKXyaihmIOM/6RKvnYS69Parrce80f4PaNpEyZLeyKuZGThmMajYqqWmUXu8ooxh0 nLY7M2iqyOkitUBviAxy4DS0co1p3vthkCYZRfG+u6N8WLQeoqEBGU8U5b0bDVfYWJQI DwGA== X-Gm-Message-State: AOAM533OsX+aKWSwr3bsFV3/7coH+DoAHGSqVmH0Cdu6y8LMmqATbKoZ qsxIAS3rmG+N3TSA3KObnVErB/Z1 X-Google-Smtp-Source: ABdhPJxgD1+a8BveVm/jwGRBERsIJsXiNRtdk6v4Wasu/B8/5PqKeW0IsySA/i6/i7RlJjRBCqmnYQ== X-Received: by 2002:ac8:73d9:: with SMTP id v25mr23795575qtp.82.1596991657622; Sun, 09 Aug 2020 09:47:37 -0700 (PDT) Received: from [10.8.0.7] ([66.115.145.34]) by smtp.gmail.com with ESMTPSA id x12sm15185963qta.67.2020.08.09.09.47.36 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sun, 09 Aug 2020 09:47:37 -0700 (PDT) Subject: Re: regdomain.xml [was also: - Linux wireless-regdb] To: freebsd-wireless@freebsd.org References: <083B7D36-2175-46DC-9C9A-FEA8673482E8@lists.zabbadoz.net> From: Aaron Message-ID: Date: Sun, 9 Aug 2020 12:47:35 -0400 User-Agent: Mozilla/5.0 (Windows NT 6.3; Win64; x64; rv:68.0) Gecko/20100101 Thunderbird/68.11.0 MIME-Version: 1.0 In-Reply-To: <083B7D36-2175-46DC-9C9A-FEA8673482E8@lists.zabbadoz.net> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US X-Rspamd-Queue-Id: 4BPlQ260YZz4CQm X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20161025 header.b=LZrMcciP; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of notjanedeere@gmail.com designates 2607:f8b0:4864:20::830 as permitted sender) smtp.mailfrom=notjanedeere@gmail.com X-Spamd-Result: default: False [-2.93 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; ARC_NA(0.00)[]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20161025]; NEURAL_HAM_MEDIUM(-1.10)[-1.100]; FROM_HAS_DN(0.00)[]; FREEMAIL_FROM(0.00)[gmail.com]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-wireless@freebsd.org]; TO_DN_NONE(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; NEURAL_HAM_LONG(-1.00)[-0.995]; RCVD_COUNT_THREE(0.00)[3]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36]; DKIM_TRACE(0.00)[gmail.com:+]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; RCVD_IN_DNSWL_NONE(0.00)[2607:f8b0:4864:20::830:from]; NEURAL_SPAM_SHORT(0.17)[0.168]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; RCVD_TLS_ALL(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim] X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 09 Aug 2020 16:47:39 -0000 The documentation portion seems like the first step, is there a wiki for proposed changes where we could start? To get started, is there any existing documentation we can refer to?  I think the answer is no, and it's down to someone who understand it going through the code to find answers ... On 8/9/2020 11:37 AM, Bjoern A. Zeeb wrote: > Hi, > > I’ll just join in on the last email in the thread not replying to > anything specific. > > Having gone through some of the stuff lately myself in order to put > [1] out (which is also includes a few things to discuss) I’ll try to > summarise a few things I’ve learnt and thought of, which confused me > over the time: > > - SKU - what does it actually stand for?   Does it really belong into > our regdomain? > > - why are the freqbands prefixes with “H”, “F”, .. and what do these > magic letters stand for? > > - We have netbands, freqbands, and bands.  None of these are actually > describing the actual frequency ranges (as the linux-db does). > > - The freqbands seems to start and end on the center frequency of the > first/last chansep spaced channel.  In the old days that was less > confusing I guess as to now with 4x20 for VHT80. > > - I am still unclear as to where we should map channels to frequency > because we are half-hearted doing that partially for upper and lower > bounds of freqbands currently.  As such I have different freqbands for > VHT20 vs. VHT40/80/160 as there are cases where there is an extra 20 > channel not part of 80s. > > - I’d love to have the freqbands actually describe the frequency > limits and have the mappings of channels within them elsewhere;  I > have no idea how/where Linux is doing that. > > - I’d love to have general freqbands and groups of them independent of > the netbands. > > - I do not actually understand what netbands are for given we have the > IEEE80211_CHAN_ set appropriately.   It’s for simplicity later but > there is a lot of duplication.  That said, some of these > IEEE80211_CHAN_* flags do not actually belong to the regulatory limits > either but are an 802.11 channel description. > > - This all leads to confusion currently as to how we setup > bands/channels/..  I made a mistake by accident and the list of > combinations we checked in ifconfig exploded to 350.000 for whether a > channel was valid.  Clearly told me that the organisation does not > seem to be right. > > - I was wondering if for clarity we can break up regdomain.xml into > multiple files? > > - One thing I don’t like on the Linux version is that for, say ETSI, > the information is basically copied per EU member state.  I love our > reference model there.  I don’t mind having etsi, etsi1, etsi2 if I > can then say 20 countries it’s etsi2 and be done.   I think that is > something essential and good we have. > > > - I do like our more structured format a lot more than the Linux one. > > - We are lacking a few things, DFS and INDOORS and maxpower are not > the only things which matter these days.  You may notice > “wmmrule=ETSI” in the Linux reg-db, for example. > > - I wonder if what we actually want is a multi-layer thingy inheriting > one from another or if we want a pure-regdomain (not knowing about > channels) and more logic elsewhere which deals with putting WiFi > things into that)? > > > - I think it’ll need a bit more than simply restructuring > regdomain.xml;  I think doing it will probably also need a bit more > (a) documentation on what each bit means and tries to accomplish) and > (b) a more clear separation between frequencies and restrictions and > 802.11 channels and with that a bit more downward code changes. > > - I would really love to see some of these things sorted and I’d love > if the thread would stay alive. > > Just my 5cts, > Bjoern > > > [1] https://reviews.freebsd.org/D25999 > _______________________________________________ > freebsd-wireless@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-wireless > To unsubscribe, send any mail to > "freebsd-wireless-unsubscribe@freebsd.org"