From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-qc0-f176.google.com (mail-qc0-f176.google.com [209.85.216.176]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by huchra.bufferbloat.net (Postfix) with ESMTPS id 59CE221F0AE for ; Fri, 27 Dec 2013 15:57:00 -0800 (PST) Received: by mail-qc0-f176.google.com with SMTP id i8so8984084qcq.21 for ; Fri, 27 Dec 2013 15:56:59 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=91i4Fyk/b4eOaX/RLOIgBej0Zkba2ok6JarnQL7YGgw=; b=mtnyQRDvzTcb1Y8tZKktDNNdCdJxGzv1179W94XCNzABY+9aCM3uaSl46iXJBLFpTI sHLqq07tCe7n5O5GHFhXwwxURQrVXuH0SEhm9kd3qprVWsFASqDNfsLtj/iHYIJqhiF2 It//GlCcbUbH85YfzQP+rqrku3bHxRGdjztMoOs3TlZKCqT02pEsqCXSH+ckIBmLKJKt gUix+cBJJrFZ+AUS9y5oMvh7MXGQ8AeNf5Cd7RrPs2nMu6+LZlpbW3d2IznT3bhhsbS7 tH1wyB/fXwOG0EqPGvfFoRemOKiLOLHEmRicn47tERgTV731tywH4kIzvuWf0AyhNLwP CK8Q== X-Gm-Message-State: ALoCoQk/CIEQLybgFVAy0T10V/yUmo638tG0de5CrYTFPPcVLRZ3ZutNC9RdL+8TcWHTVNnLK4gB MIME-Version: 1.0 X-Received: by 10.224.47.73 with SMTP id m9mr83232508qaf.23.1388188618940; Fri, 27 Dec 2013 15:56:58 -0800 (PST) Received: by 10.96.54.101 with HTTP; Fri, 27 Dec 2013 15:56:58 -0800 (PST) X-Originating-IP: [85.221.151.252] In-Reply-To: References: Date: Sat, 28 Dec 2013 00:56:58 +0100 Message-ID: From: Maciej Soltysiak To: Dave Taht Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: "cerowrt-devel@lists.bufferbloat.net" Subject: Re: [Cerowrt-devel] treating 2.4ghz as -legacy? X-BeenThere: cerowrt-devel@lists.bufferbloat.net X-Mailman-Version: 2.1.13 Precedence: list List-Id: Development issues regarding the cerowrt test router project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Dec 2013 23:57:00 -0000 I'm not too keen on the -legacy thing, because it's not language agnostic. However it seems to be a trend. At 30c3 they do exactly that: https://twitter.com/arambartholl/statuses/416612652539191296/photo/1/large Best regards, Maciej On Mon, Dec 16, 2013 at 8:46 PM, Dave Taht wrote: > I have long used "5" as an indicator that the 5ghz channel was better. > This goes back to a long thread on nanog, like 4? 5? years ago, where > the hope was to train users that "5" was better. > > Well, it's turned out that 5 is frequently better, but not always, AND > that clients tend to go for the shortest of the SSIDs available. So a > thought would be to create another ad-hoc standard for deprecating 2.4 > ghz, and have the shorter SSID be the 5ghz one. > > Ideas for the 2ghz channel: > > CEROwrt-legacy > CEROwrt2 > > I'm not huge on "legacy" because it's rather long but am stuck for > standards, I'd like a default 2.4 ghz SSID that clearly indicates the > real use to which 2.4ghz is suitable, like: > CEROwrt-GET-OFF-MY-BABY-MONITOR-YOU-FREAK > > ideas for another ssid naming standard slightly longer than a single > digit that would make sense to mom? > > -- > Dave T=C3=A4ht > > Fixing bufferbloat with cerowrt: http://www.teklibre.com/cerowrt/subscrib= e.html > _______________________________________________ > Cerowrt-devel mailing list > Cerowrt-devel@lists.bufferbloat.net > https://lists.bufferbloat.net/listinfo/cerowrt-devel