Re: [802SEC] Draft press release for review - IEEE Std 802.3bz-2016 2.5/

Thread Links	Date Links
Thread Prev	Thread Next	Thread Index	Date Prev	Date Next	Date Index

As the guy who has led the last two higher speed wireline Ethernet standards projects, I would like to thank everyone for driving more bandwidth with this email thread……

From: owner-stds-802-sec@ieee.org [mailto:owner-stds-802-sec@ieee.org] On Behalf Of Benjamin Rolfe
Sent: Thursday, October 6, 2016 3:47 PM
To: Pat Thaler <pat.thaler@BROADCOM.COM>
Cc: STDS-802-SEC@LISTSERV.IEEE.ORG
Subject: Re: [802SEC] Draft press release for review - IEEE Std 802.3bz-2016 2.5/5GBASE-T publication

I had suggested nautical mile as it is the only measurement of distance that is used consistently everywhere on earth. However Pat's suggestion is better as it acknowledges that Ethernet deployment and the influence of 802 is not limited to near proximity to the surface of Earth ;-).

On 10/6/2016 12:19 PM, Pat Thaler wrote:

Oops, I meant 233 light seconds, not years.

On Thu, Oct 6, 2016 at 12:17 PM, Pat Thaler <pat.thaler@broadcom.com> wrote:

I was going to suggest 70 gigameters because when using metric measures, one shouldn't have to deal with numbers over 1000. Or one could go with 233 light years.

:^)

Really I agree with John. And the important point is that there is really quite a lot of that cable out there so it doesn't matter much if someone misunderstands which definition of "billion" is in play.

On Thu, Oct 6, 2016 at 9:03 AM, Benjamin Rolfe <ben@blindcreek.com> wrote:

I suggest that "70 billion meters" be changed to 37796976.2419 nautical miles (kmi) to avoid confusion of "meter" with a measuring device.

;-)

On 10/6/2016 2:35 AM, Law, David wrote:

Dear EC members,

Please find attached an update draft IEEE Std 802.3bz-2016 2.5/5GBASE-T publication press release based on the comments from John below. I've also attached a compare to show the changes from the original.

In respect to the use of the word 'billion', despite many creative suggestions including 'enough cable to reach from Earth to Mars during next year's opposition' I've been persuaded that '70 billion meters' should be used due to the reasons John lists.

I therefore propose to move to an email ballot on this draft.

Best regards,

  David

-----Original Message-----

From: Law, David

Sent: 03 October 2016 08:59

To: IEEE 802 SEC <stds-802-sec@ieee.org> <stds-802-sec@ieee.org>

Subject: RE: [802SEC] Draft press release for review - IEEE Std 802.3bz-2016 2.5/5GBASE-T publication

Hi John,

I should have said that I agreed with Roger's suggestion to change from 'm' to 'km' to avoid the use of the word 'Billion' due to the potential differences in interpretation between one thousand million (10^9) and one million million (10^12) in some geographies. That being said I take your point and will work off-line with you on this and the other item.

Best regards,

  David

-----Original Message-----

From: John D'Ambrosia [mailto:jdambrosia@gmail.com]

Sent: 03 October 2016 00:54

To: Law, David <dlaw@hpe.com>; 'IEEE 802 SEC <stds-802-sec@ieee.org>' <stds-802-sec@IEEE.ORG>

Subject: RE: [802SEC] Draft press release for review - IEEE Std 802.3bz-2016 2.5/5GBASE-T publication

David,

I have to disagree with Roger on the change from "m" to "km".  There are two

reasons for this - 1) the BASE-T standard has always been discussed in terms

of m, such as 100m; 2) there is a lot of press already going about the 70

Billion m, which I suggest gets echoed.

 I also note that there is a singular reference to gigabit per second, but

in the context of this PR it is somewhat meaningless.  1000BASE-T is

considered by many to be the most successful Ethernet standard - which has

blazed the path for this standard.

John

-----Original Message-----

From: owner-stds-802-sec@ieee.org [mailto:owner-stds-802-sec@ieee.org] On

Behalf Of Law, David

Sent: Sunday, October 2, 2016 12:49 PM

To: IEEE 802 SEC <stds-802-sec@ieee.org> <stds-802-sec@IEEE.ORG>

Subject: Re: [802SEC] Draft press release for review - IEEE Std 802.3bz-2016

2.5/5GBASE-T publication

Dear EC members,

Please find attached an update draft IEEE Std 802.3bz-2016 2.5/5GBASE-T

publication press release based on the comments from Roger below. I've

attached both a clean and compare version to show the changes made.

Best regards,

  David

-----

From: Roger Marks [mailto:r.b.marks@ieee.org]

Sent: 01 October 2016 00:14

To: Law, David <dlaw@hpe.com>

Cc: SEC STDS-802-SEC <STDS-802-SEC@listserv.ieee.org>

Subject: Re: [802SEC] Draft press release for review - IEEE Std 802.3bz-2016

2.5/5GBASE-T publication

David,

I have a couple of editorial suggestions:

(1) Instead of "70 billion meters", how about "70 million kilometers"? When

people talk about a lot of meters, they are usually referring to some kind

of measuring instruments.

(2) "project being approved" => "project initiated"

(3) "so that enterprise interconnect solutions for wireless access points

can switch applications served over structured Category 5e or better twisted

pair cabling" => "so that enterprise interconnections over structured

Category 5e, or better, twisted pair cabling can support modern wireless

access points without compromise"

Roger

Law, David wrote:

Dear EC members,

Based on consultation with the IEEE-SA PR agency, the attached press release

has been drafted in anticipation of the publication of IEEE Std 802.3bz-2016

2.5/5GBASE-T which was approved as an IEEE Standard on 22nd September 2016.

Since the development of this press release was at the request of the Task

Force Chair and myself I'm seeking EC approval.

I am therefore circulating the attached draft for comment and have asked

that approval of this release be placed on the IEEE 802 802 EC interim

teleconference consent agenda.

Thanks and best regards,

  David

----------

This email is sent from the 802 Executive Committee email reflector.  This

list is maintained by Listserv.

----------

This email is sent from the 802 Executive Committee email reflector.  This

list is maintained by Listserv.

----------

This email is sent from the 802 Executive Committee email reflector.  This list is maintained by Listserv.

---------- This email is sent from the 802 Executive Committee email reflector. This list is maintained by Listserv.