throbber
User Requirements for
`Cabling Support
`
`Robert D. Love
`LAN Connect Consultants
`
`Dave Kooistra
`IBM
`
`May 24-25, 2000
`802.3af Ottawa
`
`Rdlove@ieee.org
`kooistra@us.ibm.com
`
`Juniper Ex 1041-p. 1
`Juniper v ChriMar
`IPR2016-01397
`
`

`

`Dealing with Past Cabling
`Choices and with Ethernet’s
`Success
`
`May 24-25, 2000
`802.3af Ottawa
`
`Rdlove@ieee.org
`kooistra@us.ibm.com
`
`Juniper Ex 1041-p. 2
`Juniper v ChriMar
`IPR2016-01397
`
`

`

`Cabling Mix Within the Enterprise
`
`• 100% UTP - Most small and mid size
`organizations
`– New installations primarily 4-pair Cat 5 or 5e
`– Old installations Cat 3, 2-pair, 3-pair, 4-pair
`
`May 24-25, 2000
`802.3af Ottawa
`
`Rdlove@ieee.org
`kooistra@us.ibm.com
`
`Juniper Ex 1041-p. 3
`Juniper v ChriMar
`IPR2016-01397
`
`

`

`Cabling Mix Within the Enterprise
`
`• 100% UTP - Most small and mid size
`organizations
`• Mostly UTP, some STP - A few mid-size
`and many large organizations
`• Mostly STP - a few large organizations
`– e.g.. IBM has an estimated 1/2 million STP
`drops
`
`May 24-25, 2000
`802.3af Ottawa
`
`Rdlove@ieee.org
`kooistra@us.ibm.com
`
`Juniper Ex 1041-p. 4
`Juniper v ChriMar
`IPR2016-01397
`
`

`

`Cabling Mix Implications
`• With mixed cabling infrastructure
`– Solutions are sought that run over the entire
`spectrum of installed cabling
`• Legacy cabling is still an important to the
`end users
`– Need to support legacy cable can affect
`decision for entire enterprise
`– Premature replacement adds cost without
`increasing function
`
`May 24-25, 2000
`802.3af Ottawa
`
`Rdlove@ieee.org
`kooistra@us.ibm.com
`
`Juniper Ex 1041-p. 5
`Juniper v ChriMar
`IPR2016-01397
`
`

`

`Are there emerging
`requirements?
`• In parts of Europe use of two pair shielded
`100 ohm cabling to an outlet was and still is
`a popular choice - allowed by IS11801
`• Emerging Cat 7 cabling systems are being
`purchased with the expectation of
`supporting multiple applications with 2-pair
`per outlet
`
`May 24-25, 2000
`802.3af Ottawa
`
`Rdlove@ieee.org
`kooistra@us.ibm.com
`
`Juniper Ex 1041-p. 6
`Juniper v ChriMar
`IPR2016-01397
`
`

`

`CIO Objectives
`• Introduce applications based on need, and in
`part, on their ability to be replicated
`throughout the enterprise
`• Replace cabling plants that can not robustly
`support required applications
`• Choose minimum total cost solutions
`
`May 24-25, 2000
`802.3af Ottawa
`
`Rdlove@ieee.org
`kooistra@us.ibm.com
`
`Juniper Ex 1041-p. 7
`Juniper v ChriMar
`IPR2016-01397
`
`

`

`CIO Expectations
`• For large enterprises they can expect to
`have to support both legacy 2-pair cabling
`plants, and possibly new 2-pair installations,
`in addition to 4-pair wiring
`
`May 24-25, 2000
`802.3af Ottawa
`
`Rdlove@ieee.org
`kooistra@us.ibm.com
`
`Juniper Ex 1041-p. 8
`Juniper v ChriMar
`IPR2016-01397
`
`

`

`What Technical Solutions
`Address User Requirements?
`
`• Where 4-pair cabling is available, the 4-pair
`only solution meets requirements
`• If 4-pair are not available, then a 2-pair
`solution is the only one that will save the
`costs of re-cabling
`
`• Make sure any solution can be applied to
`legacy 2-pair as well as 4-pair cabling!
`
`May 24-25, 2000
`802.3af Ottawa
`
`Rdlove@ieee.org
`kooistra@us.ibm.com
`
`Juniper Ex 1041-p. 9
`Juniper v ChriMar
`IPR2016-01397
`
`

This document is available on Docket Alarm but you must sign up to view it.


Or .

Accessing this document will incur an additional charge of $.

After purchase, you can access this document again without charge.

Accept $ Charge
throbber

Still Working On It

This document is taking longer than usual to download. This can happen if we need to contact the court directly to obtain the document and their servers are running slowly.

Give it another minute or two to complete, and then try the refresh button.

throbber

A few More Minutes ... Still Working

It can take up to 5 minutes for us to download a document if the court servers are running slowly.

Thank you for your continued patience.

This document could not be displayed.

We could not find this document within its docket. Please go back to the docket page and check the link. If that does not work, go back to the docket and refresh it to pull the newest information.

Your account does not support viewing this document.

You need a Paid Account to view this document. Click here to change your account type.

Your account does not support viewing this document.

Set your membership status to view this document.

With a Docket Alarm membership, you'll get a whole lot more, including:

  • Up-to-date information for this case.
  • Email alerts whenever there is an update.
  • Full text search for other cases.
  • Get email alerts whenever a new case matches your search.

Become a Member

One Moment Please

The filing “” is large (MB) and is being downloaded.

Please refresh this page in a few minutes to see if the filing has been downloaded. The filing will also be emailed to you when the download completes.

Your document is on its way!

If you do not receive the document in five minutes, contact support at support@docketalarm.com.

Sealed Document

We are unable to display this document, it may be under a court ordered seal.

If you have proper credentials to access the file, you may proceed directly to the court's system using your government issued username and password.


Access Government Site

We are redirecting you
to a mobile optimized page.





Document Unreadable or Corrupt

Refresh this Document
Go to the Docket

We are unable to display this document.

Refresh this Document
Go to the Docket