From: Ulrich Speidel <u.speidel@auckland.ac.nz>
To: Michael Richardson <mcr@sandelman.ca>
Cc: "starlink@lists.bufferbloat.net" <starlink@lists.bufferbloat.net>
Subject: Re: [Starlink] Blog on Tonga cable
Date: Wed, 2 Mar 2022 10:53:02 +1300 [thread overview]
Message-ID: <fbdfb620-1fff-eae3-b4c6-209260b78be5@auckland.ac.nz> (raw)
In-Reply-To: <12643.1646154747@localhost>
Usually, you would cut either side of the cable on top and then put the
splice on top of that cable and leave the cut piece on the seafloor.
Pulling out from underneath would likely cause damage to the cable on
top. That said, damage close to crossover sites is very rare: For one,
damage to cables in deep water is actually a rare event - many systems
run for decades without a fault - and most cable systems have few if any
crossover points.
In this case, the Hawaiki cable was actually laid after the Fiji-Tonga
cable, so Hawaiki is on top, however the recent damage on the Fiji-Tonga
cable was a significant distance to the east of Hawaiki, so it wasn't
impacted. In fact, there are plans for a Hawaiki spur to Tonga's
northern island group of Vava'u (and microwave links from there to
Ha'apai and down to Tongatapu / 'Eua).
On 2/03/2022 6:12 am, Michael Richardson wrote:
> Looking at the diagram in the blog entry, I see how Australia/NZ<->Hawaii
> cable crosses the Tongatupu/Suava cable.
> How does cable repair work when there is another cable "on top"?
--
****************************************************************
Dr. Ulrich Speidel
School of Computer Science
Room 303S.594 (City Campus)
The University of Auckland
u.speidel@auckland.ac.nz
http://www.cs.auckland.ac.nz/~ulrich/
****************************************************************
prev parent reply other threads:[~2022-03-01 21:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-28 23:11 Ulrich Speidel
2022-03-01 17:12 ` Michael Richardson
2022-03-01 21:53 ` Ulrich Speidel [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.bufferbloat.net/postorius/lists/starlink.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=fbdfb620-1fff-eae3-b4c6-209260b78be5@auckland.ac.nz \
--to=u.speidel@auckland.ac.nz \
--cc=mcr@sandelman.ca \
--cc=starlink@lists.bufferbloat.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox