; dumb older switch.
They're fragile but they're not _that_ fragile. A switch that can't
figure out 10 mbps half duplex... now that's fragile.
-Bill
--
William Herrin her...@dirtside.com b...@herrin.us
Dirtside Systems . Web: <http://www.dirtside.com/>
I only need one outlet to be remotely power cycle-able. I have one piece of
> equipment that is occasionally a little flaky and, well, you know the hassle.
The ancient (read: cheap used) APC AP9211's still get the job done.
Regards,
Bill Herrin
--
William Herrin
t adjacent, the
packet expires before it reaches your router. If it reaches your
router with a TTL larger than 1 and you haven't enabled bgp multihop
then the packet is discarded. Changing BGP's semantics like this
requires cooperation and expertise from your ISP and is likely to be
b
nless there's an active inbound call with the same caller id.
Regards,
Bill Herrin
--
William Herrin her...@dirtside.com b...@herrin.us
Dirtside Systems . Web: <http://www.dirtside.com/>
ed off for reasons I can't quite articulate, so I asked: "Are you
a robot or a person?" She responded "yes" and then launched in to a
sales pitch. The next time I asked, "where can I direct your call?"
She responded "that's good" and launched
hina
(which forbids transferring addresses back) as long as the recipient
met the registry requirements... Not ARIN's registry requirements,
China's.
Regards,
Bill Herrin
--
William Herrin her...@dirtside.com b...@herrin.us
Dirtside Systems . Web: <http://www.dirtside.com/>
ready to pay the cost
of multihoming you truly won't have any trouble justifying an ARIN
/24.
Regards,
Bill Herrin
--
William Herrin her...@dirtside.com b...@herrin.us
Dirtside Systems . Web: <http://www.dirtside.com/>
lve
itself in routing disputes. Your upstream (and their upstream, et
cetera) will act to preserve their reputations. If that includes
manually blocking some of your announcements, you'll have a devil of a
time undoing it later.
Regards,
Bill Herrin
--
William Herrin her..
m line hasn't: it's
ridiculously consumptive.
Regards,
Bill Herrin
--
William Herrin her...@dirtside.com b...@herrin.us
Dirtside Systems . Web: <http://www.dirtside.com/>
ite or
not? e.g. "telnet tierii.iema.state.il.us 80"
Regards,
Bill Herrin
--
William Herrin her...@dirtside.com b...@herrin.us
Dirtside Systems . Web: <http://www.dirtside.com/>
to like it, but there it is.
If you contacted the POC and the POC replied stop, you stop. If the
POC was hijacked at the RIR, that's between your customer and the RIR.
The RIR has a standard process and an expert team for dealing with
these situations. It's their job.
Regards,
Bill Herr
blished POC by email, by
phone and if necessary by postal mail. Until you get a response to the
query YOU initiated to the POC, stick with the status quo.
Regards,
Bill Herrin
--
William Herrin her...@dirtside.com b...@herrin.us
Dirtside Systems . Web: <http://www.dirtside.com/>
of each state in which they operate.
When they use only private rights of way (e.g. railroad tracks) they
are generally unregulated.
Regards,
Bill Herrin
--
William Herrin her...@dirtside.com b...@herrin.us
Dirtside Systems . Web: <http://www.dirtside.com/>
a nickel. If
someone steals my bitcoin wallet, I'm f**.
Given the cost of renumbering, we'd have to be insane to depend on
blockchain for address management.
Regards,
Bill Herrin
--
William Herrin her...@dirtside.com b...@herrin.us
Dirtside Systems . Web: <http://www.dirtside.com/>
On Tue, Jan 23, 2018 at 8:17 AM, Jimmy Hess wrote:
> On Tue, Jan 9, 2018 at 10:22 AM, William Herrin wrote:
>
>> On Tue, Jan 9, 2018 at 1:07 AM, John R. Levine wrote:
>>
>>
> The promise of blockchain is fraud-resistant recordkeeping, database
> management,
>
plaint that they can't get to your web site from home, but can from
work (or vice versa). Your web site is "obviously" working and the
calls are infrequent, so support advises there's a problem with the
customer's ISP.
Regards,
Bill Herrin
--
William Herrin
On Fri, Jan 19, 2018 at 8:58 AM, Jared Mauch wrote:
>> On Jan 18, 2018, at 8:44 PM, William Herrin wrote:
>>> Which packet? Is there a specific CDN that does this? I’d be curious to
>>> see
>>> data vs speculation.
>>
>> Path MTU discovery (whi
of defense in depth), a host
is only permitted to communicate with whitelisted IP addresses. Random
Internet routers are not on the whitelist.
PMTUD's routine failure demonstrates the wisdom of the end to end
principle. It's the one critical place in base IPv4 that doesn't follow
On Thu, Jan 18, 2018 at 7:41 PM, Jared Mauch wrote:
>> On Jan 18, 2018, at 7:32 PM, William Herrin wrote:
>>
>> On Thu, Jan 18, 2018 at 7:14 PM, Jared Mauch wrote:
>>> lets say i can
>>> send you a 9K packet. If you receive that frame, and realize you
he host you were looking for.
Good luck.
Regards,
Bill Herrin
P.S. This makes Linux servers happy:
iptables -t mangle --insert POSTROUTING --proto tcp \
--tcp-flags SYN,RST,FIN SYN --match tcpmss --mss 1241:65535 \
--jump TCPMSS --set-mss 1240
--
William Herrin
Dale W. Carder wrote:
>
> Traceroute or any other path diagnostics comes to mind.
That's not obvious to me. Assuming the time-exceeded message was modified
to include the necessary data, how would blockchain authenticate the
responding router?
Regards,
Bill Herrin
--
William He
olved by
ordinary PKI.
Now, if we wanted to replace the RIRs and allow people to self-assign IPv6
addresses out of ULA space which we'd then honor in the global BGP table,
blockchain could have a role.
-Bill
--
William Herrin her...@dirtside.com b...@herrin.
in RFC1918.
Other than that, it's exactly the same as RFC 1918.
Site local is deprecated. As explained in the RFC, the concept of a "site"
could not be usefully defined for the purpose of private addressing. You
can safely ignore it.
Regards,
Bill Herrin
--
William Herrin ..
of custody, but when do you need to do
that in computer networking?
Regards,
Bill Herrin
--
William Herrin her...@dirtside.com b...@herrin.us
Dirtside Systems . Web: <http://www.dirtside.com/>
On Sun, Jan 7, 2018 at 8:57 PM, Masataka Ohta <
mo...@necom830.hpcl.titech.ac.jp> wrote:
> William Herrin wrote:
>
>> Meltdown and Spectre are privilege escalation flaws. If you can induce the
>> physical hardware to run arbitrary code you provide at an unprivileged
>&
hes generally do not run untrusted
code so the preconditions for Meltdown and Spectre generally aren't there.
Regards,
Bill Herrin
--
William Herrin her...@dirtside.com b...@herrin.us
Dirtside Systems . Web: <http://www.dirtside.com/>
an "I can't
afford $5k." The former is a legitimate business decision that businesses
make every day.
-Bill
--
William Herrin her...@dirtside.com b...@herrin.us
Dirtside Systems . Web: <http://www.dirtside.com/>
is not in the Internet business or any other
kind of business and should probably stop lying to themselves about that.
Regards,
Bill Herrin
--
William Herrin her...@dirtside.com b...@herrin.us
Dirtside Systems . Web: <http://www.dirtside.com/>
On Thu, Jan 4, 2018 at 4:02 PM, Dan Hollis wrote:
> On Thu, 4 Jan 2018, William Herrin wrote:
>
>> On Thu, Jan 4, 2018 at 11:48 AM, Michael Crapse
>> wrote:
>>
>>> I've never dealt with a support queue that resolved the issue faster than
>>> a
hase under $5000 and the ARIN justification for that small a
block almost writes itself.
Regards,
Bill Herrin
--
William Herrin her...@dirtside.com b...@herrin.us
Dirtside Systems . Web: <http://www.dirtside.com/>
hey need a plan other than "advertise to your
peers with BGP" because even if your peer accepts a /27, most of their
peers will not.
Regards,
Bill Herrin
--
William Herrin her...@dirtside.com b...@herrin.us
Dirtside Systems . Web: <http://www.dirtside.com/>
ptimal routing from most origins.
Regards,
Bill Herrin
--
William Herrin her...@dirtside.com b...@herrin.us
Dirtside Systems . Web: <http://www.dirtside.com/>
the support queue to the guy
competent to deal with my problem is one of the more infuriating things
about big company support.
-Bill
--
William Herrin her...@dirtside.com b...@herrin.us
Dirtside Systems . Web: <http://www.dirtside.com/>
bmission
should provide a case number, the individual to whom it is assigned, direct
contact information for that individual and a promise that your report will
receive a response.
Regards,
Bill Herrin
--
William Herrin her...@dirtside.com b...@herrin.us
Dirtside Systems . Web: <http://www.dirtside.com/>
rom such action would have to exceed the risk.
Regards,
Bill Herrin
--
William Herrin her...@dirtside.com b...@herrin.us
Dirtside Systems . Web: <http://www.dirtside.com/>
o line.
Regards,
Bill Herrin
--
William Herrin her...@dirtside.com b...@herrin.us
Dirtside Systems . Web: <http://www.dirtside.com/>
to be in the GRT" - that's why we have Private AS numbers.
>
Private AS numbers suffer from the same interconnection collision issues as
private IP addresses and if you have a private AS it's *because* you're
interconnecting networks.
Regards,
Bill Herrin
--
William He
d other 'things' we can't
> even imagine right now.
>
Think in terms of system architectures where the address space is fully
consumed when empty to more than 20 decimal places. Because we're idiots
and actually designed it that way.
--
William Herrin
r that feeds a
-48 battery system. You connect your equipment the battery and make sure
the rectifier system puts out enough wattage to both power the equipment
and keep the battery topped off.
Try searching ebay for "rack rectifier"
Regards,
Bill Herrin
--
William Herrin ...
eader.
The originating and destination nodes have to pay attention to all
extension headers, but then they always did have to process packets with
information of variable lengths.
Regards,
Bill Herrin
--
William Herrin her...@dirtside.com b...@herrin.us
Dirtside Systems . Web: <http://www.dirtside.com/>
begin a new "classless" era for IPv6. The short of it is, we got here
> first, so we don't have to give a shit about being efficient or frugal.
>
Yep.
Regards,
Bill Herrin
--
William Herrin her...@dirtside.com b...@herrin.us
Dirtside Systems . Web: <http://www.dirtside.com/>
;
> One might consider Hulu et al not so at-fault with that fact in
> consideration.
Hi Jima,
Net 196/8 is part of the swamp. Just speculating, but perhaps the original
registration of 196.53.96.0/22 pre-dated the reassignment of 196/8 to
AfriNIC?
Regards,
Bill Herrin
--
William Herrin her...@dirtside.com b...@herrin.us
Dirtside Systems . Web: <http://www.dirtside.com/>
all you really
need is for the right person at Hulu to receive a swift kick in the tail
from someone they can't ignore.
Regards,
Bill Herrin
--
William Herrin her...@dirtside.com b...@herrin.us
Dirtside Systems . Web: <http://www.dirtside.com/>
l it's fixed? :)
Good luck with that since the BGP session collapses in the process of
receiving that corrupted data. That's the bug. The other guy's router could
filter the prefix but if he doesn't he fouls the BGP session to everybody
he tries to peer it to
On Fri, Dec 22, 2017 at 5:45 PM, Nick Hilliard wrote:
> William Herrin wrote:
> > The AS path lengths we're talking about are unreasonable.
>
> "unreasonable" is a peculiar word to use here :-)
>
> It's the internet and you can't expect other peo
Regards,
Bill Herrin
--
William Herrin her...@dirtside.com b...@herrin.us
Dirtside Systems . Web: <http://www.dirtside.com/>
protocol, works as well as anything new that
could be designed.
Regards,
Bill Herrin
--
William Herrin her...@dirtside.com b...@herrin.us
Dirtside Systems . Web: <http://www.dirtside.com/>
not worry about how many bits are consumed at this step." With a cumulative
effect on the consumption of IPv6 space.
Regards,
Bill Herrin
--
William Herrin her...@dirtside.com b...@herrin.us
Dirtside Systems . Web: <http://www.dirtside.com/>
another order of
magnitude. It slips away faster than you might think.
Regards,
Bill Herrin
--
William Herrin her...@dirtside.com b...@herrin.us
Dirtside Systems . Web: <http://www.dirtside.com/>
e
doing it wrong. You know who you are.
If this seems inconsistent with my last email, my key point there was not
that we're using IPv6 in a crazy way (although to some extent we are) but
rather that the IPv6 address space is by tens of orders of magnitude much
smaller than you think.
Regard
with 2000::/3 right
now. After we burn through that in the next 20 years, we can if we so
desire change the rules for how (and how quickly) we use 4000::/3.
Regards,
Bill Herrin
--
William Herrin her...@dirtside.com b...@herrin.us
Dirtside Systems . Web: <http://www.dirtside.com/>
emi-clever because the .0 address is a corner case in the code
and corner cases are where bugs are most likely to happen. And if you're
sending clients from that address to another host with a regular 172.16
address anyway...
Regards,
Bill Herrin
>
>
> Original message -
;s about
as clear as mud. First you asked about routing. Now you imply HTTP.
Regards,
Bill Herrin
--
William Herrin her...@dirtside.com b...@herrin.us
Dirtside Systems . Web: <http://www.dirtside.com/>
tatic-routed anycast address?
2. In what reachability context? Is this a private network? An ISP network
where the reachability should be the ISP and its customers?
Regards,
Bill Herrin
--
William Herrin her...@dirtside.com b...@herrin.us
Dirtside Systems . Web: <http://www.dirtside.com/>
petently, or building an unsafe raised floor.).
>
I want pictures of the unsafe raised floor.
-Bill
--
William Herrin her...@dirtside.com b...@herrin.us
Dirtside Systems . Web: <http://www.dirtside.com/>
hey almost immediately spread throughout the office.
That's bad, so we use different cable than what we put under the desk where
the fumes will tend to stay near where they started.
Trap gases? No! Plenum is for where the gases would quickly spread!
Regards,
Bill Herrin
--
Willi
but I don't recall much in the way of
oversight... or banishment.
I do recall that the '88 Morris worm resulted in 400 hours of community
service and a tenured professorship at MIT. I suppose the latter could be
considered a severe consequence.
Regards,
Bill Herrin
--
William He
burst power usage.)
A Cisco 2911 or 3945 does this though the 3945 is a little more power
hungry.
A current generation x86 server running Linux and Quagga does this.
Regards,
Bill Herrin
--
William Herrin her...@dirtside.com b...@herrin.us
Dirtside Systems ...
t's not a demo meant to get you to pay for
it then you're not the customer, you're the product. If you're the product,
guess what the customer is paying for.
Regards,
Bill Herrin
--
William Herrin her...@dirtside.com b...@herrin.us
Dirtside Systems . Web: <http://www.dirtside.com/>
uring negotiation means
the application should "check for captive portal."
--
William Herrin her...@dirtside.com b...@herrin.us
Dirtside Systems . Web: <http://www.dirtside.com/>
om a particular
address don't especially exist and would be much more complex. Systemic and
computational complexity is a very practical difference between the two
situations.
Regards,
Bill Herrin
--
William Herrin her...@dirtside.com b...@herrin.us
Dirtside Systems . Web: <http://www.dirtside.com/>
On Wed, Nov 29, 2017 at 12:17 PM, Stephen Frost wrote:
> * William Herrin (b...@herrin.us) wrote:
> > On Wed, Nov 29, 2017 at 12:03 PM, Eric Kuhnke
> wrote:
> > > How much weight do you put on an incoming message, in terms of adding
> > > additional score towards
ards a possible value of spam, for total absence of
> DKIM signature?
>
Zero. DKIM for mailing lists is a horribly broken design and legitimate
mailing lists are second only to spam in quantity of SMTP transactions.
Regards,
Bill Herrin
--
William Herrin her...@dirtsid
t
the IP level. Underlying transits at the Ethernet or MPLS level are
intentionally invisible to the endpoints.
Regards,
Bill Herrin
--
William Herrin her...@dirtside.com b...@herrin.us
Dirtside Systems . Web: <http://www.dirtside.com/>
which isn't about the FCC action per say.
>
> This is about how does one define Transit provider vs ISP ?
Corn on the cob vs. corn in a can.
> Just curious to see if there are agreed upon definitions from the
> network operators's point of view.
No.
Regards,
Bill
are identified in such a way
that multiple consumers for the same data request the same chunk ID. And
small enough chunks that real-time feeds are delayed by few enough seconds
to make them practical.
Unicast with a little bit of anycast. No multicast on that road map.
Regards,
Bill Herri
tructure as well as laying out the combatants' duties to
mitigate collateral damage from strikes on government personnel and
facilities? Is there some reason these laws should not continue to apply
when the attacks are carried out with bits instead of bombs?
Regards,
Bill Herrin
--
William Herrin
On Thu, Oct 26, 2017 at 3:05 PM, William Herrin wrote:
> On Thu, Oct 26, 2017 at 2:47 PM, Jason Lixfeld
> wrote:
> You'd only use communities like that if you want to signal the ISP to
> deprioritize your advertisement on a particular peer or set of peers but
> not others
On Thu, Oct 26, 2017 at 2:47 PM, Jason Lixfeld
wrote:
> Hi Bill,
>
> > On Oct 26, 2017, at 2:37 PM, William Herrin wrote:
> >
> > BGP routing is based on "distance". Distance in BGP is primarily
> calculated as the number of ASNs in the AS Path. Prepends mak
ch path gets
taken.
Is this a relic from before ISPs allowed for local preference adjustment,
> or is there actually a use case for this?
It's the exact opposite of a relic.
Regards,
Bill Herrin
--
William Herrin her...@dirtside.com b...@herrin.us
Dirtside Systems . Web: <http://www.dirtside.com/>
r the top of the cabinets and back in to your servers. You can't
necessarily fill a cabinet with equipment. When you reach the allowable
heat density, you have to start filling the next cabinet. I've seen DC
cabinets left half empty for exactly this reason.
Regards,
Bill Herrin
--
Will
DCs' palm vein databases is lost, what's your plan for replacing that hand?
Regards,
Bill Herrin
--
William Herrin her...@dirtside.com b...@herrin.us
Dirtside Systems . Web: <http://www.dirtside.com/>
beyond what was later
generalized with CIDR, it's not obvious.
10.0: 1010
172.16: 1010 1100 0001
172.31: 1010 1100 0001
192.168: 1100 1010 1000
AFAIK, it was simply one range each from classes A, B and C.
Regards,
Bill Herrin
--
William Herrin .
On Sun, Oct 1, 2017 at 1:06 PM, Kelly Dowd wrote:
> On Sun, Oct 1, 2017 at 12:29 AM, William Herrin wrote:
>
>> To the chucklehead who started announcing a 2200+ byte AS path yesterday
>> around 18:27 EDT, I beg of you: STOP. You've triggered a bug in Quagga
>>
>
it sends to the neighbor who then chokes.
Bug and patch here:
https://lists.quagga.net/pipermail/quagga-dev/2017-September/033284.html
Regards,
Bill Herrin
--
William Herrin her...@dirtside.com b...@herrin.us
Dirtside Systems . Web: <http://www.dirtside.com/>
h --enable-pcreposix I believe it supports the
regex. Most installs that come straight from a Linux distro used this flag.
Regards,
Bill
--
William Herrin her...@dirtside.com b...@herrin.us
Dirtside Systems . Web: <http://www.dirtside.com/>
XXX
bgp maxas-limit 50
Juniper:
https://kb.juniper.net/InfoCenter/index?page=content&id=KB29321
Quagga:
ip as-path access-list maxas-limit50 deny ^([{},0-9]+ ){50}
ip as-path access-list maxas-limit50 permit .*
Regards,
Bill Herrin
--
William Herrin her...@dirtside.
ns' identifiers. When you build your central database, make sure
it can accept the arbitrary circuit ID formats applied to your new property.
Regards,
Bill Herrin
--
William Herrin her...@dirtside.com b...@herrin.us
Dirtside Systems . Web: <http://www.dirtside.com/>
er. Put the customer's configuration (such as
speed) in your database and leave it out of the circuit id.
Regards,
Bill Herrin
--
William Herrin her...@dirtside.com b...@herrin.us
Dirtside Systems . Web: <http://www.dirtside.com/>
g table which is NOT
BCP38.
Strict mode URPF down paths guaranteed to be single-homed. Manually
configure allowed sources and announcements for BGP-talking customers.
Regards,
Bill Herrin
--
William Herrin her...@dirtside.com b...@herrin.us
Dirtside Systems . Web: <http://www.dirtside.com/>
s a valley where the participating
organization is not paid for or directly donating the transiting packets.
Regards,
Bill Herrin
--
William Herrin her...@dirtside.com b...@herrin.us
Dirtside Systems . Web: <http://www.dirtside.com/>
kage in the peering link could jam traffic between your customers and
theirs. If you're not able to notice and respond, you'd be better off
sending the traffic up to your ISPs and letting them worry about it.
If the three of those add up to "yes" instead of &quo
of the 32 departments. Delegation on nibble boundaries
> is for convience and nothing else.
>
For comprehensibility which nets convenience. Consistently delegate on
nibble boundaries and your power users don't have to understand Boolean
algebra to make sense of the network.
Regards
ir students? ARIN will generally accept
either explanation. You'll get the larger number of IPv6 addresses you want
if you tell them you're an ISP.
The cost difference is likely to remain minimal. The major issue is that as
an ISP you'll be expected to enter SWIP records so read up
not /64. IPv6 can do nifty IoT things like
collecting all of a guest's devices behind his personal firewall but it
doesn't work if you've only assigned a /64.
Regards,
Bill Herrin
--
William Herrin her...@dirtside.com b...@herrin.us
Dirtside Systems . Web: <http://www.dirtside.com/>
k you to stop.
Regards,
Bill Herrin
--
William Herrin her...@dirtside.com b...@herrin.us
Dirtside Systems . Web: <http://www.dirtside.com/>
v6 reverse DNS also delegates on the nibble boundary.
Heck, I’m gonna do whatever it takes to NOT subnet on bits with my v6
> deployment. Hopefully with v6, gone are the days of binary subnetting math.
>
Good plan.
-Bill
--
William Herrin her...@dirtside.com b...@herrin
s of /124 over /126. And /124 doesn't
suffer from ND exhaustion attacks like /112 might. The only thing /112 buys
you (that I can see) is a single colon in front of the final digit. I don't
see how /112 would be a good choice.
Regards,
Bill Herrin
--
William Herrin her..
e worse I suppose. They could have picked 113.
-Bill
--
William Herrin her...@dirtside.com b...@herrin.us
Dirtside Systems . Web: <http://www.dirtside.com/>
On Wed, Jun 28, 2017 at 5:09 PM, Thomas Bellman wrote:
> On 2017-06-28 17:03, William Herrin wrote:
>
> > The common recommendations for IPv6 point to point interface numbering
> are:
> > /64
> > /124
> > /126
> > /127
>
> I thought the only allowe
for any loss
> or damage arising in any way from the use thereof.The term "PRIMUS"
> includes its affiliates.
>
>
> Pour la version en français de ce message, veuillez voir
> http://www.primustel.ca/fr/legal/cs.htm
>
--
William Herrin her...@dirtside.com b...@herrin.us
Dirtside Systems . Web: <http://www.dirtside.com/>
ly can't do much to limit the BGP announcements because it's often
impractical to determine whether a block of IP addresses can legitimately
be announced from a given peer.
Regards,
Bill Herrin
--
William Herrin her...@dirtside.com b...@herrin.us
Dirtside Systems . Web: <http://www.dirtside.com/>
arize if I get any
general-interest information.
Regards,
Bill Herrin
--
William Herrin her...@dirtside.com b...@herrin.us
Dirtside Systems . Web: <http://www.dirtside.com/>
On Wed, Mar 29, 2017 at 12:24 PM, Alan Hodgson
wrote:
> On Wednesday 29 March 2017 11:12:33 William Herrin wrote:
> > Both SPF and DKIM are meant to be checked against the domain in the
> > envelope sender (SMTP protocol-level return address) which the NANOG list
> &g
was scored by spam assassin as "SPF_PASS" even though you do not
include NANOG's servers in the SPF record for tnetconsulting.net.
Regards,
Bill Herrin
--
William Herrin her...@dirtside.com b...@herrin.us
Dirtside Systems . Web: <http://www.dirtside.com/>
l.
>
Hello,
Both SPF and DKIM are meant to be checked against the domain in the
envelope sender (SMTP protocol-level return address) which the NANOG list
sets to nanog-boun...@nanog.org. Checking against the message header "from"
address is an incorrect implementation which will brea
I tried it, the servers which the glue claims are authoritative
for a zone could assert that they themselves are not authoritative and
offer new glue for completely different servers asserted to be
authoritative. I had to fake a parent zone in Bind. This was before DNSSEC.
Regards,
Bill
Bill Herrin
--
William Herrin her...@dirtside.com b...@herrin.us
Dirtside Systems . Web: <http://www.dirtside.com/>
Thanks for the clarification!
Regards,
Bill Herrin
--
William Herrin her...@dirtside.com b...@herrin.us
Dirtside Systems . Web: <http://www.dirtside.com/>
On Fri, Mar 17, 2017 at 1:42 PM, Mark Kosters wrote:
> On 3/17/17, 12:26 PM, "NANOG on behalf of William Herrin" <
nanog-boun...@nanog.org on behalf of b...@herrin.us> wrote:
>> Hmm. That sounds like an ARIN-side bug too. ARIN's code responded to
>> co
701 - 800 of 1967 matches
Mail list logo
