/blogs/routing-configuration-over-dhcpv6-2/
The presented examples use values 242 for NEXT_HOP and 243
for RTPREFIX option codes.
Don't you want to increase the number of operators endorsing the
private assignments?
Masataka Ohta
).
Masataka Ohta
What will happen to .uk if England is left alone?
Masataka Ohta
of site.
Masataka Ohta
are everywhere
and we need something like DNS to translate names into
something scalably routable, that is, hierarchical
addresses.
Masataka Ohta
.
Masataka Ohta
as slow as that of IPv6.
Even 4G entry will not be a problem, except that it may cause BGP
update computation slower.
Masataka Ohta
be compromised.
And carrying TSIG key in DHCP reply is just secure from the both
sides.
Not in the clear it isn't.
Clear text in DHCP reply is just secure when required security
level allows to use DHCP.
Masataka Ohta
recommended a person, and the
person recommended by NSA.
Masataka Ohta
to
hire to replace them, and your top troubleshooter?
Feel free to hunt witches if you think it necessary.
Masataka Ohta
obscurity with worse security.
Masataka Ohta
PS
If the server and its clients share some secret for mutual
authentication as protection against snooping, there is no
point to make forward and reverse DNS secure.
themselves.
And carrying TSIG key in DHCP reply is just secure from the both sides.
Masataka Ohta
going away to US through US based companies.
It is expensive only for those having foreign servers, which
nullifies advantages of global service companies over domestic
ones.
Masataka Ohta
related
local regulations as long as they want to have business
at the locale.
Masataka Ohta
.
Masataka Ohta
and directly
connected with modest security, which makes automation possible.
Masataka Ohta
the DHCP packet to it.
Masataka Ohta
there is no NAT, the key
to update rDNS must, naturally, be contained only in DHCP reply
to the CPE.
And, I'm afraid your draft assumes that the CPE behaves as a
DHCP server for local hosts, which means the CPE is responsible
for rDNS registration.
Masataka
.
Masataka Ohta
and a lot more practical just to
use shared secret between a CPE and a ISP's name server
for TSIG generation.
As the secret can be directly shared end to end, it is more
secure than DNSSEC involving untrustworthy third parties.
Masataka Ohta
requirement for any security
between two parties.
Masataka Ohta
.
Masataka Ohta
in the companies can argue against.
Unless they are fired and all the backdoors installed by
them are removed, neither Yahoo and Google are secure.
Masataka Ohta
access line encrypted (by a manually
configured password), which makes DHCP packets invisible.
Masataka Ohta
sniffer on the street outside.
Does your CPE retransmit a received DHCP reply to Wifi?
Masataka Ohta
.
Masataka Ohta
host name, the old rules for HOSTS.TXT should be followed.
both of should in the rfc should, today, be interpreted as MUST.
Masataka Ohta
, security by plain DNS with reverse look up is
fine.
Masataka Ohta
valdis.kletni...@vt.edu wrote:
Legal enforcement on zone administrators makes related zones
insecure.
Citation, please?
Snowden.
Masataka Ohta
TR Shaw wrote:
Major update provides many of 5S functionality to the 5, 4S, 4
Different versions could have been updated on different days,
at least.
Masataka Ohta
.
Masataka Ohta
IPv6 option that has the Option Type highest-order two
bits set to 10), or
which makes it necessary, unless you are idiots, to filter ICMPv6
PTB against certain packets, including but not limited to,
multicast ones.
Masataka Ohta
with /40 or /48 prefix means 16M entry CAM, which is hard,
which is why IPv6 is hard.
Masataka Ohta
to reduce the number of routing
table entries exchanged between adjacent ASes.
Masataka Ohta
approach a half million
prefixes.
True. And that's why we must avoid IPv6.
Masataka Ohta
.
Masataka Ohta
it is impractical to assume an IP address can be mapped
uniquely to a geolocation.
Masataka Ohta
end-site
announcements can be worst than that...
See 5.2. Limiting the Number of TLAs of my draft.
Anyway... Drifting off-topic for this thread.
Current poor support for multihomed sites is a reason why
BCP38 is not operational.
Masataka Ohta
mapping system.
Masataka Ohta
unbundling is, seemingly, most
competitive against BT.
Masataka Ohta
download music data etc. with examples of
xDSL, CATV and Wifi.
Masataka Ohta
reality that PON is more expensive
than SS and insist on stating it were my opinion without any
evidences, its your arrogance.
PERIOD.
Masataka Ohta
is a lot worse than mine.
Sorry, but, it is your problem.
Keep on this track and you're just going to be ignored by
most people on the list.
I'm afraid it is also your problem to be suffered by you.
Masataka Ohta
and now we
are getting FTTC this March apparently...
Obviously because it makes L1 unbundling difficult.
Masataka Ohta
and a large closures containing the splitters
of PON can not be shared by two or more subscribers, which means
PON incurs much more material and labor cost for each initial
subscriber than SS.
Masataka Ohta
initial
subscriber than SS.
Masataka Ohta
for 192 subscribers, because with 8:1, you
only need 24 trunk fibers and 7 drop fibers.
Your theory is not consistent with the reality.
Masataka Ohta
, if they allow three other
competitors share its cable.
So, there is no reason to simply have SS just with small
closures, which can be trivially unbundled.
Masataka Ohta
you accept 110bps dial up good
enough.
Masataka Ohta
PS
You can, of course, pay for private satellite connectivity
at certain bps available world wide.
and investments.
Anyway, as SS is less expensive than PON, there is no reason to
insist on PON.
Masataka Ohta
seen.
Except for length, size and cost, there is not much difference.
They all are to have drop cables.
Masataka Ohta
number of subscribers sharing a splitter in field is 3.68,
a little less than 4, from:
http://itpro.nikkeibp.co.jp/article/COLUMN/20080619/308665/
Masataka Ohta
engineering was clearly assigned to the madogiwazoku if
they're only getting a 4:1 split on average.
Of course, anyone who try to use PON for FTTH is madogiwazoku like
you.
Masataka Ohta
. Fiber, fdh, splitters, etc... are marginal.
You never forget labor cost.
Installing more lengthy drop cable, in addition to trunk cable,
means more labor.
Installing a bulky PON closure with splitter means more labor.
Masataka Ohta
(including both trunk
and drop).
Note also that sharing a drop cable between multiple subscribers
is virtually impossible.
Or am I dense?
Feel free to call yourself so.
Masataka Ohta
on the trunk, allowing you to spec smaller cables.
That is a negligible part of the cost. Cable cost is not very
sensitive to the number of fibers in a cable.
Masataka Ohta
Masataka Ohta wrote:
Assume you have 4000 subscribers and total trunk cable length
Correction. Though I wrote 4000, it is a population and the number
of subscribers are 1150.
For example, if drop cables of PON are 10m longer in average than
that of SS, it's total length is 40km, which
required only
for PON.
Note that the splitters cost even if they are located in field.
Masataka Ohta
to point will have 1 strand per home passed. But the
lengths should be the same, shouldn't they ?
Never ignore topology at the last yards.
Masataka Ohta
cost 311K JPY, whereas SS cost 304K JPY,
even though SS case is about twice less subsrriber density
(28.8 vs 16.2 subscribers/km2).
Masataka Ohta
with considerable share, L1
unbundling costs less.
They can just have routers, switches and DSL modems in
collocation spaces of COs, without L2TP or PPPoE, which
means they can eliminate cost for L2TP or PPPoE.
Masataka Ohta
by the
infrastructure operator or another ISP already present on
site. But some tends to stick to L1 service and deply
their own eqipments for many reasons.
Masataka Ohta
with power and
cooling units to enable any ISP yo install active equipments (either OLT
or ethernet switch).
How is the wiring between the concentration points and residences?
Masataka Ohta
operator in Japan is not tier 1.
Its simply a different world and despite your belief L2
unbundling is not a poor alternative.
It's poor because it's less unbundled and needs extra equipments
unnecessary for real competitors.
Masataka Ohta
always, because, without
the room, you can not replace copper cables without much service
interruption.
To replace a damaged copper cable without much service
interruption, you have to lay a new cable before removing the
damaged cable.
Masataka Ohta
an Ethernet VLAN,
Frame Relay PVC, etc complete with QoS. I assume XO,
etc use UNE access to the local loop. There is no reason
a Muni can't do something similar.
Muni can. However, there is no reason Muni can't offer L1
unbundling.
Masataka Ohta
allows ILECs choose stupid L2 technologies such
as ATM or PON, which is locally best for their short term
revenue, which, in the long run, delays global deployment of
broadband environment, because of high cost to the customers.
Masataka Ohta
.
Masataka Ohta
attaching
optical fibers to silicon, is a key piece of Luxtera's
intellectual property. We think of a laser as being just
like a DC power supply – only it provides a steady stream of
photons rather than electrons.
Masataka
has to wait days/weeks with end user without service?
Masataka Ohta
over almost immediately.
See above.
Masataka Ohta
network
is very different (different requirements) than for a greenfield muni
system.
Surely, transition from copper to fiber is not trivial, but it
helps a lot that fiber cables are thinner than copper cables.
Masataka Ohta
or two (or three, maybe) shared light source in CO can
have much better quality, which can be distributed to all
the transmitters using splitters and EDFA, which does not
consume a lot of power.
Masataka Ohta
.
Masataka Ohta
William Herrin wrote:
The governments in question are watching for exfiltration and they
largely use a less risky approach: they issue their own root key and,
That is a trusted first party.
Masataka Ohta
modified EUI-64 format aof rfc4291.
We should better introduce partially decimal format for
IPv6 addresses or, better, avoid IPv6 entirely.
Masataka Ohta
Another option would be to do both. Assign a fixed address and also
let it chose EUI-64
dropped
unconditionally along some paths.
Again, it is not a problem of tunnels only.
If that is the operational reality, specifications on
fragmentation must be dropped from IPv6 specification.
Masataka Ohta
than 20% of packets will be dropped and effective speed
share of each TCP will be decreased by 30%.
The proper approach against lossy liks is to have link local
retransmissions or FEC.
Masataka Ohta
enables a zone
containing just a CNAME, though RFC1034 does not specify so.
It is not harmful except that queries with SOA or NS type may
cause loops if some cache have CNAME RRs.
Masataka Ohta
reason is that 1Tbps packet needs 100 times shorter
delay lines to buffer than 10Gbps ones.
Above describes your setting for the next protocol. There is not
a lot of leeway in design space, I'm afraid.
Just keep using IPv4.
Masataka Ohta
PS
See
not work.
If you do it in optics the protocol is completely different
from IPv4/IPv6,
What I have shown is that what will be completely different will
be L2.
IPv4 uber alles.
Masataka Ohta
talking about initial-fragment vs non-initial fragments? -- If
so, in theory *both* might be missing the upper layer information.
Yes, that is one of an annoying point of IPv6.
Masataka Ohta
?
http://www.peering-forum.eu/assets/presentations2012/JunpierEPF7.pdf
But, it does not say much about 100G.
Masataka Ohta
or 16*25GE is no worse than
actually trunked 400GE with 40*10G or 16*25G.
While slide #12 mentions 50Gbps per lane, it is too often impossible
to be as practical as the Ethernet today.
Masataka Ohta
and allows
for very large skew.
Masataka Ohta
circumstances, 100GE with 4*25G may
become less expensive than 10*10GE.
But, as it is unlikely that 1TE will be 4*250G or 400GE will
be 2*200G, faster Ethernet has little, if any, economical merit.
Masataka Ohta
clients can't talk to each other at layer 2,
regardless of how that annoys layer 3.
It means IPv6 is broken over not only WiFi but also Ethernet.
Does this bother you?
No, not me, not at all.
Masataka Ohta
demonstrated to work just fine.
Tell it to IETF to modify SLAAC to exclude DAD.
Masataka Ohta
David Miller wrote:
So, a single example of IPv4 behaving in a suboptimal manner would be
enough to declare IPv4 not operational?
For example?
Masataka Ohta
, that is a
sub-optimal operation.
In this thread, there is an example of such an operation to
have a lot of WiFi base stations with omnidirectional antennas
at full power.
No protocol can be fool proof against sub-optimal operations.
Masataka Ohta
.
Masataka Ohta
valuable
than, Dood, IPv6 has problems on wifi networks.
The only thing operators have to know about IPv6 is that IPv6, as
is currently specified, is not operational.
Then, let IETF bother.
Masataka Ohta
at all.
Masataka Ohta
client-server DHCP was broadcast
Of course.
However, at WiFi L2, it is first unicast to AP and then broadcast
by the AP.
Masataka Ohta
.
Masataka Ohta
but as a protocol for the entire
Internet.
Masataka Ohta
the ~IPv6 over Foo series of
documents is all about, accommodating those needs ...
Because ND uber Alles is impossible, IPv6 over Foo
series specifying ND parameters are not helpful.
Masataka Ohta
to defend IPv6, you must say multicast RA and
DAD are unnecessary features of IPv6, which means the current
IPv6 is broken.
Masataka Ohta
of packet loss
You don't understand CSMA/CA at all.
There aren't so much packet losses except for broadcast/multicast
packets.
Masataka Ohta
attempt to have SLAAC, which resulted in so stateful and time
wasting mechanism.
As it is virtually impossible to remember IPv6 addresses, IPv6
operation is a lot harder than necessary.
Masataka Ohta
401 - 500 of 654 matches
Mail list logo
