{"id":120,"date":"2006-01-27T00:00:00","date_gmt":"2006-01-27T00:00:00","guid":{"rendered":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/2006\/01\/27\/gartner-says-dont-deploy-802-11n-until-2007\/"},"modified":"2021-12-30T11:36:33","modified_gmt":"2021-12-30T11:36:33","slug":"gartner-says-dont-deploy-802-11n-until-2007","status":"publish","type":"post","link":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/2006\/01\/27\/gartner-says-dont-deploy-802-11n-until-2007\/","title":{"rendered":"Gartner Says Don\u2019t Deploy 802.11n until 2007"},"content":{"rendered":"<p>Companies should stay away from next-generation Wi-Fi equipment described as 802.11n compliant, Gartner has warned.   Expect these technology investments to be good for at least four more years,&#8221; a group of three Gartner analysts recommended, adding that 802.11n should not be considered until 2007.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>VBroadcom and Marvell have already announced that they will start producing &#8216;draft-compliant&#8217; chipsets, but Gartner labelled these claims as &#8220;misleading&#8221; and &#8220;premature&#8221;.<\/p>\n<p>The analyst firm believes that the technology is likely to be changed before a final standard is approved, and that additional testing will be required to ensure compatibility with existing Wi-Fi standards.<\/p>\n<p>http:\/\/www.vnunet.com\/vnunet\/news\/2149265\/gartner-pleads-restraint-802<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-120","post","type-post","status-publish","format-standard","hentry","category-uncategorized"],"_links":{"self":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/120","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/comments?post=120"}],"version-history":[{"count":1,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/120\/revisions"}],"predecessor-version":[{"id":2607,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/120\/revisions\/2607"}],"wp:attachment":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/media?parent=120"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/categories?post=120"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/tags?post=120"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}