[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

IP and Optical domains?

Subject: IP and Optical domains?
From: mohta at necom830.hpcl.titech.ac.jp (Masataka Ohta)
Date: Wed, 22 Jun 2016 18:58:51 +0900
In-reply-to: <[email protected]>
References: <CAPLq3UNr1R=wwYwhPpL+3EgFekotZY0P6y-Fgu4rNhgyn3Vf3A@mail.gmail.com> <[email protected]> <[email protected]> <[email protected]> <[email protected]> <[email protected]> <[email protected]>

Mark Tinka wrote:

>> By not managing transport characteristics at all except
>> that links are on or off (or, if you want to guarantee QoS,
>> a little more than that).
>
> But how do Layer 3 protocols manage transport characteristics today?

Today??? You asked "can be better designed", didn't you?

And, don't miss the following assumption:

 > L3 HELO generated frequently enough.

 > Again, this does not seem too removed from what happens already today.

The problem, if any, is that doing much more than that
results in "heavily underutilized" network.

 > I don't disagree with what you imply by "heavily".

The implication is not mine.

						Masataka Ohta

Follow-Ups:
- IP and Optical domains?
  - From: mark.tinka at seacom.mu (Mark Tinka)

References:
- IP and Optical domains?
  - From: glen.kent at gmail.com (Glen Kent)
- IP and Optical domains?
  - From: mohta at necom830.hpcl.titech.ac.jp (Masataka Ohta)
- IP and Optical domains?
  - From: mark.tinka at seacom.mu (Mark Tinka)
- IP and Optical domains?
  - From: mohta at necom830.hpcl.titech.ac.jp (Masataka Ohta)
- IP and Optical domains?
  - From: mark.tinka at seacom.mu (Mark Tinka)
- IP and Optical domains?
  - From: mohta at necom830.hpcl.titech.ac.jp (Masataka Ohta)
- IP and Optical domains?
  - From: mark.tinka at seacom.mu (Mark Tinka)

Prev by Date: Google Geolocation issue
Next by Date: IP and Optical domains?
Previous by thread: IP and Optical domains?
Next by thread: IP and Optical domains?
Index(es):
- Date
- Thread