Special Counsel Office report web site
The Special Counsel's report is expected to be posted on its website sometime between 11 a.m. and noon on Thursday, April 18, 2019. https://www.justice.gov/sco Since I helped with website for the Starr Report on September 11, 1998, I wish all website admins and network admins well tommorrow morning. # config t ip go faster
On Apr 17, 2019, at 9:02 PM, Sean Donelan <sean@donelan.com> wrote:
The Special Counsel's report is expected to be posted on its website sometime between 11 a.m. and noon on Thursday, April 18, 2019.
Since I helped with website for the Starr Report on September 11, 1998, I wish all website admins and network admins well tommorrow morning.
# config t ip go faster
Sean: I remember “ip go faster” when you first posted it back in 1998. It was hilarious, I literally “LOL”ed. However, I did not envy you your job with that short notice. (But I did envy you all the people who were willing to help on such short notice.) I am still impressed at what you were able to pull together in just a few days. Major Kudos. Things will probably be easier this time. The Internet has evolved ways of dealing with exactly this problem. (Avi used to call it “slash-dot insurance”, but the idea is the same.) Specifically: TiggerBook-C-32:~ patrick$ dig +short www.justice.gov www.justice.gov.edgekey.net. e7598.dscg.akamaiedge.net. ’Nuff said. -- TTFN, patrick
On Wed, 17 Apr 2019, Patrick W. Gilmore wrote:
Things will probably be easier this time. The Internet has evolved ways of dealing with exactly this problem. (Avi used to call it “slash-dot insurance”, but the idea is the same.) Specifically:
Yep, it will be interesting to see where the chokepoints are tommorrow. In 1998, the bandwidth pipes never filled up. The chokepoint was in the TCP and Web stacks. Eventually the Associated Press got a copy of the Starr Report on a CD from a congressional staffer. The press intern running down the street holding a CD was faster than 1998 internet :-) We were also lucky in 1998, no one had thought of DDOS yet.
And we may still see the web stack being the ultimate cause of the delay. Parkinson's law always comes to the rescue:-) More faster and efficient processing architecture, Hyper transport buses, amd-64 Branch prediction. Massively faster storage subsystems and disk arrays, SSD slab caching for hypervisors And some dude with a AJAX framework to serve a PDF bringging the whole thing to a a screeching halt On April 17, 2019 10:35:29 PM EDT, Sean Donelan <sean@donelan.com> wrote:
On Wed, 17 Apr 2019, Patrick W. Gilmore wrote:
Things will probably be easier this time. The Internet has evolved ways of dealing with exactly this problem. (Avi used to call it “slash-dot
insurance”, but the idea is the same.) Specifically:
Yep, it will be interesting to see where the chokepoints are tommorrow.
In 1998, the bandwidth pipes never filled up. The chokepoint was in the
TCP and Web stacks. Eventually the Associated Press got a copy of the Starr Report on a CD from a congressional staffer. The press intern running down the street holding a CD was faster than 1998 internet :-)
We were also lucky in 1998, no one had thought of DDOS yet.
Frederick Wessling (CIO) Succinct Systems LLC Cell: +1(561) 571-2799 Office: +1(904) 758-9915 ext. 9925 Fax: +1(904) 758-9987 www.SuccinctSystems.com
of course p2p is the way to distribute this but i doubt the justice department can admit there is any positive legitimate use for p2p. (i’ve been surprised that it hasn’t made it to wikileaks or bittorrent yet. “russiar, are you listening?”) (i sure hope there’s a signed version or at least a hash.) i predict there will be versions with fake content, missing content, and malware inserted that are distributed as well. and i’ll bet there will be some infected pdf version as well distributed that way. On Apr 17, 2019, 7:57 PM -0700, fwessling--- via NANOG <nanog@nanog.org>, wrote:
And we may still see the web stack being the ultimate cause of the delay.
Parkinson's law always comes to the rescue:-) More faster and efficient processing architecture, Hyper transport buses, amd-64 Branch prediction. Massively faster storage subsystems and disk arrays, SSD slab caching for hypervisors
And some dude with a AJAX framework to serve a PDF bringging the whole thing to a a screeching halt
On April 17, 2019 10:35:29 PM EDT, Sean Donelan <sean@donelan.com> wrote:
On Wed, 17 Apr 2019, Patrick W. Gilmore wrote:
Things will probably be easier this time. The Internet has evolved ways of dealing with exactly this problem. (Avi used to call it “slash-dot
insurance”, but the idea is the same.) Specifically:
Yep, it will be interesting to see where the chokepoints are tommorrow.
In 1998, the bandwidth pipes never filled up. The chokepoint was in the
TCP and Web stacks. Eventually the Associated Press got a copy of the Starr Report on a CD from a congressional staffer. The press intern running down the street holding a CD was faster than 1998 internet :-)
We were also lucky in 1998, no one had thought of DDOS yet.
Frederick Wessling (CIO) Succinct Systems LLC Cell: +1(561) 571-2799 Office: +1(904) 758-9915 ext. 9925 Fax: +1(904) 758-9987 www.SuccinctSystems.com
Isn’t this why god invented CDNs? Though, i doubt the govment is Akamized... -Mike
On Apr 17, 2019, at 20:26, Mark Seiden <mis@seiden.com> wrote:
of course p2p is the way to distribute this but i doubt the justice department can admit there is any positive legitimate use for p2p.
(i’ve been surprised that it hasn’t made it to wikileaks or bittorrent yet. “russiar, are you listening?”)
(i sure hope there’s a signed version or at least a hash.)
i predict there will be versions with fake content, missing content, and malware inserted that are distributed as well.
and i’ll bet there will be some infected pdf version as well distributed that way.
On Apr 17, 2019, 7:57 PM -0700, fwessling--- via NANOG <nanog@nanog.org>, wrote: And we may still see the web stack being the ultimate cause of the delay.
Parkinson's law always comes to the rescue:-) More faster and efficient processing architecture, Hyper transport buses, amd-64 Branch prediction. Massively faster storage subsystems and disk arrays, SSD slab caching for hypervisors
And some dude with a AJAX framework to serve a PDF bringging the whole thing to a a screeching halt
On April 17, 2019 10:35:29 PM EDT, Sean Donelan <sean@donelan.com> wrote:
On Wed, 17 Apr 2019, Patrick W. Gilmore wrote: Things will probably be easier this time. The Internet has evolved ways of dealing with exactly this problem. (Avi used to call it “slash-dot
insurance”, but the idea is the same.) Specifically:
Yep, it will be interesting to see where the chokepoints are tommorrow.
In 1998, the bandwidth pipes never filled up. The chokepoint was in the
TCP and Web stacks. Eventually the Associated Press got a copy of the Starr Report on a CD from a congressional staffer. The press intern running down the street holding a CD was faster than 1998 internet :-)
We were also lucky in 1998, no one had thought of DDOS yet.
Frederick Wessling (CIO) Succinct Systems LLC Cell: +1(561) 571-2799 Office: +1(904) 758-9915 ext. 9925 Fax: +1(904) 758-9987 www.SuccinctSystems.com
Check the nANOG archives for examples of whitehouse.gov, cia.gov etc. It certainly is. On Wed, Apr 17, 2019 at 23:34 <mike.lyon@gmail.com> wrote:
Isn’t this why god invented CDNs? Though, i doubt the govment is Akamized...
-Mike
On Apr 17, 2019, at 20:26, Mark Seiden <mis@seiden.com> wrote:
of course p2p is the way to distribute this but i doubt the justice department can admit there is any positive legitimate use for p2p.
(i’ve been surprised that it hasn’t made it to wikileaks or bittorrent yet. “russiar, are you listening?”)
(i sure hope there’s a signed version or at least a hash.)
i predict there will be versions with fake content, missing content, and malware inserted that are distributed as well.
and i’ll bet there will be some infected pdf version as well distributed that way. On Apr 17, 2019, 7:57 PM -0700, fwessling--- via NANOG <nanog@nanog.org>, wrote:
And we may still see the web stack being the ultimate cause of the delay.
Parkinson's law always comes to the rescue:-) More faster and efficient processing architecture, Hyper transport buses, amd-64 Branch prediction. Massively faster storage subsystems and disk arrays, SSD slab caching for hypervisors
And some dude with a AJAX framework to serve a PDF bringging the whole thing to a a screeching halt
On April 17, 2019 10:35:29 PM EDT, Sean Donelan <sean@donelan.com> wrote:
On Wed, 17 Apr 2019, Patrick W. Gilmore wrote:
Things will probably be easier this time. The Internet has evolved
ways
of dealing with exactly this problem. (Avi used to call it “slash-dot
insurance”, but the idea is the same.) Specifically:
Yep, it will be interesting to see where the chokepoints are tommorrow.
In 1998, the bandwidth pipes never filled up. The chokepoint was in the
TCP and Web stacks. Eventually the Associated Press got a copy of the Starr Report on a CD from a congressional staffer. The press intern running down the street holding a CD was faster than 1998 internet :-)
We were also lucky in 1998, no one had thought of DDOS yet.
Frederick Wessling (CIO) Succinct Systems LLC Cell: +1(561) 571-2799 Office: +1(904) 758-9915 ext. 9925 Fax: +1(904) 758-9987 www.SuccinctSystems.com
Or maybe do this (faster than nanog archives) :) bash-3.2# dig cia.gov ns ; <<>> DiG 9.10.6 <<>> cia.gov ns ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 33203 ;; flags: qr rd ra ad; QUERY: 1, ANSWER: 6, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 4096 ;; QUESTION SECTION: ;cia.gov. IN NS ;; ANSWER SECTION: cia.gov. 86400 IN NS a22-66.akam.net. cia.gov. 86400 IN NS a16-67.akam.net. cia.gov. 86400 IN NS a1-22.akam.net. cia.gov. 86400 IN NS a12-65.akam.net. cia.gov. 86400 IN NS a3-64.akam.net. cia.gov. 86400 IN NS a13-65.akam.net.
On Apr 17, 2019, at 9:11 PM, Martin Hannigan <hannigan@gmail.com> wrote:
Check the nANOG archives for examples of whitehouse.gov <http://whitehouse.gov/>, cia.gov <http://cia.gov/> etc. It certainly is.
On Wed, Apr 17, 2019 at 23:34 <mike.lyon@gmail.com <mailto:mike.lyon@gmail.com>> wrote: Isn’t this why god invented CDNs? Though, i doubt the govment is Akamized...
-Mike
On Apr 17, 2019, at 20:26, Mark Seiden <mis@seiden.com <mailto:mis@seiden.com>> wrote:
of course p2p is the way to distribute this but i doubt the justice department can admit there is any positive legitimate use for p2p.
(i’ve been surprised that it hasn’t made it to wikileaks or bittorrent yet. “russiar, are you listening?”)
(i sure hope there’s a signed version or at least a hash.)
i predict there will be versions with fake content, missing content, and malware inserted that are distributed as well.
and i’ll bet there will be some infected pdf version as well distributed that way. On Apr 17, 2019, 7:57 PM -0700, fwessling--- via NANOG <nanog@nanog.org <mailto:nanog@nanog.org>>, wrote:
And we may still see the web stack being the ultimate cause of the delay.
Parkinson's law always comes to the rescue:-) More faster and efficient processing architecture, Hyper transport buses, amd-64 Branch prediction. Massively faster storage subsystems and disk arrays, SSD slab caching for hypervisors
And some dude with a AJAX framework to serve a PDF bringging the whole thing to a a screeching halt
On April 17, 2019 10:35:29 PM EDT, Sean Donelan <sean@donelan.com <mailto:sean@donelan.com>> wrote:
On Wed, 17 Apr 2019, Patrick W. Gilmore wrote:
Things will probably be easier this time. The Internet has evolved ways of dealing with exactly this problem. (Avi used to call it “slash-dot
insurance”, but the idea is the same.) Specifically:
Yep, it will be interesting to see where the chokepoints are tommorrow.
In 1998, the bandwidth pipes never filled up. The chokepoint was in the
TCP and Web stacks. Eventually the Associated Press got a copy of the Starr Report on a CD from a congressional staffer. The press intern running down the street holding a CD was faster than 1998 internet :-)
We were also lucky in 1998, no one had thought of DDOS yet.
Frederick Wessling (CIO) Succinct Systems LLC Cell: +1(561) 571-2799 Office: +1(904) 758-9915 ext. 9925 Fax: +1(904) 758-9987 www.SuccinctSystems.com <http://www.succinctsystems.com/>
Oh spiffy! Will be interesting to see if there are any problems then. -Mike
On Apr 17, 2019, at 21:14, Brett Watson <brett@the-watsons.org> wrote:
Or maybe do this (faster than nanog archives) :)
bash-3.2# dig cia.gov ns
; <<>> DiG 9.10.6 <<>> cia.gov ns ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 33203 ;; flags: qr rd ra ad; QUERY: 1, ANSWER: 6, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 4096 ;; QUESTION SECTION: ;cia.gov. IN NS
;; ANSWER SECTION: cia.gov. 86400 IN NS a22-66.akam.net. cia.gov. 86400 IN NS a16-67.akam.net. cia.gov. 86400 IN NS a1-22.akam.net. cia.gov. 86400 IN NS a12-65.akam.net. cia.gov. 86400 IN NS a3-64.akam.net. cia.gov. 86400 IN NS a13-65.akam.net.
On Apr 17, 2019, at 9:11 PM, Martin Hannigan <hannigan@gmail.com> wrote:
Check the nANOG archives for examples of whitehouse.gov, cia.gov etc. It certainly is.
On Wed, Apr 17, 2019 at 23:34 <mike.lyon@gmail.com> wrote: Isn’t this why god invented CDNs? Though, i doubt the govment is Akamized...
-Mike
On Apr 17, 2019, at 20:26, Mark Seiden <mis@seiden.com> wrote:
of course p2p is the way to distribute this but i doubt the justice department can admit there is any positive legitimate use for p2p.
(i’ve been surprised that it hasn’t made it to wikileaks or bittorrent yet. “russiar, are you listening?”)
(i sure hope there’s a signed version or at least a hash.)
i predict there will be versions with fake content, missing content, and malware inserted that are distributed as well.
and i’ll bet there will be some infected pdf version as well distributed that way.
On Apr 17, 2019, 7:57 PM -0700, fwessling--- via NANOG <nanog@nanog.org>, wrote: And we may still see the web stack being the ultimate cause of the delay.
Parkinson's law always comes to the rescue:-) More faster and efficient processing architecture, Hyper transport buses, amd-64 Branch prediction. Massively faster storage subsystems and disk arrays, SSD slab caching for hypervisors
And some dude with a AJAX framework to serve a PDF bringging the whole thing to a a screeching halt
On April 17, 2019 10:35:29 PM EDT, Sean Donelan <sean@donelan.com> wrote: > On Wed, 17 Apr 2019, Patrick W. Gilmore wrote: > Things will probably be easier this time. The Internet has evolved ways > of dealing with exactly this problem. (Avi used to call it “slash-dot
> insurance”, but the idea is the same.) Specifically:
Yep, it will be interesting to see where the chokepoints are tommorrow.
In 1998, the bandwidth pipes never filled up. The chokepoint was in the
TCP and Web stacks. Eventually the Associated Press got a copy of the Starr Report on a CD from a congressional staffer. The press intern running down the street holding a CD was faster than 1998 internet :-)
We were also lucky in 1998, no one had thought of DDOS yet.
Frederick Wessling (CIO) Succinct Systems LLC Cell: +1(561) 571-2799 Office: +1(904) 758-9915 ext. 9925 Fax: +1(904) 758-9987 www.SuccinctSystems.com
Hey Mike. Agreed. But the scale of a 400 page document with global interest? Should be highly cached with a good ratio of served to pull bits. I'm willing to bet you a beer its just another day on the Internet. However, I could be wrong. Hope to see you in DC to collect! I already know Brett is in. :) Best, -M< On Thu, Apr 18, 2019 at 12:21 AM <mike.lyon@gmail.com> wrote:
Oh spiffy!
Will be interesting to see if there are any problems then.
-Mike
On Apr 17, 2019, at 21:14, Brett Watson <brett@the-watsons.org> wrote:
Or maybe do this (faster than nanog archives) :)
bash-3.2# dig cia.gov ns
; <<>> DiG 9.10.6 <<>> cia.gov ns ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 33203 ;; flags: qr rd ra ad; QUERY: 1, ANSWER: 6, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 4096 ;; QUESTION SECTION: ;cia.gov. IN NS
;; ANSWER SECTION: cia.gov. 86400 IN NS a22-66.akam.net. cia.gov. 86400 IN NS a16-67.akam.net. cia.gov. 86400 IN NS a1-22.akam.net. cia.gov. 86400 IN NS a12-65.akam.net. cia.gov. 86400 IN NS a3-64.akam.net. cia.gov. 86400 IN NS a13-65.akam.net.
On Apr 17, 2019, at 9:11 PM, Martin Hannigan <hannigan@gmail.com> wrote:
Check the nANOG archives for examples of whitehouse.gov, cia.gov etc. It certainly is.
On Wed, Apr 17, 2019 at 23:34 <mike.lyon@gmail.com> wrote:
Isn’t this why god invented CDNs? Though, i doubt the govment is Akamized...
-Mike
On Apr 17, 2019, at 20:26, Mark Seiden <mis@seiden.com> wrote:
of course p2p is the way to distribute this but i doubt the justice department can admit there is any positive legitimate use for p2p.
(i’ve been surprised that it hasn’t made it to wikileaks or bittorrent yet. “russiar, are you listening?”)
(i sure hope there’s a signed version or at least a hash.)
i predict there will be versions with fake content, missing content, and malware inserted that are distributed as well.
and i’ll bet there will be some infected pdf version as well distributed that way. On Apr 17, 2019, 7:57 PM -0700, fwessling--- via NANOG <nanog@nanog.org>, wrote:
And we may still see the web stack being the ultimate cause of the delay.
Parkinson's law always comes to the rescue:-) More faster and efficient processing architecture, Hyper transport buses, amd-64 Branch prediction. Massively faster storage subsystems and disk arrays, SSD slab caching for hypervisors
And some dude with a AJAX framework to serve a PDF bringging the whole thing to a a screeching halt
On April 17, 2019 10:35:29 PM EDT, Sean Donelan <sean@donelan.com> wrote:
On Wed, 17 Apr 2019, Patrick W. Gilmore wrote:
Things will probably be easier this time. The Internet has evolved
ways
of dealing with exactly this problem. (Avi used to call it “slash-dot
insurance”, but the idea is the same.) Specifically:
Yep, it will be interesting to see where the chokepoints are tommorrow.
In 1998, the bandwidth pipes never filled up. The chokepoint was in the
TCP and Web stacks. Eventually the Associated Press got a copy of the Starr Report on a CD from a congressional staffer. The press intern running down the street holding a CD was faster than 1998 internet :-)
We were also lucky in 1998, no one had thought of DDOS yet.
Frederick Wessling (CIO) Succinct Systems LLC Cell: +1(561) 571-2799 Office: +1(904) 758-9915 ext. 9925 Fax: +1(904) 758-9987 www.SuccinctSystems.com <http://www.succinctsystems.com/>
On Thu, Apr 18, 2019 at 12:25:32AM -0400, Martin Hannigan wrote:
Hey Mike.
Agreed. But the scale of a 400 page document with global interest? Should be highly cached with a good ratio of served to pull bits. I'm willing to bet you a beer its just another day on the Internet. However, I could be wrong. Hope to see you in DC to collect! I already know Brett is in. :)
I would expect far more traffic from patch tuesday to exceed the size of the document. - Jared -- Jared Mauch | pgp key available via finger from jared@puck.nether.net clue++; | http://puck.nether.net/~jared/ My statements are only mine.
Agreed, I remember the biggest problem when the Starr Report was released was that our dial-up PoPs had all lines busy. It was a different Internet then. Steven Naslund Chicago IL
Hey Mike.
Agreed. But the scale of a 400 page document with global interest? Should be highly cached with a good ratio of served to pull bits. I'm willing to bet you a beer its just another day on the Internet. However, I could be wrong. Hope to see you in DC to collect! I already know Brett is in. :)
B&N just announced that they are offering free downloads via their Nook reader. I noticed I couldn’t reach B&N via IPv6, and discovered the cause : nslookup
set type=AAAA barnesandnoble.com Server: 4.2.2.1 Non-authoritative answer: *** Can't find barnesandnoble.com: No answer
set type=A barnesandnoble.com. Server: 4.2.2.1 Non-authoritative answer: Name: barnesandnoble.com Address: 161.221.74.213
I don’t know if this is a temporary DNS failure, or B&N really still has no IPv6 hosted web services :) -mel
On Apr 18, 2019, at 6:46 AM, Naslund, Steve <SNaslund@medline.com> wrote:
Agreed, I remember the biggest problem when the Starr Report was released was that our dial-up PoPs had all lines busy. It was a different Internet then.
Steven Naslund Chicago IL
Hey Mike.
Agreed. But the scale of a 400 page document with global interest? Should be highly cached with a good ratio of served to pull bits. I'm willing to bet you a beer its just another day on the Internet. However, I could be wrong. Hope to see you in DC to collect! I already know Brett is in. :)
Oops..the link would be helpful, sorry! We have made the full report available here, including conclusions (full report both embedded by iframe, and linked to the actual report at DOJ). https://www.theinternetpatrol.com/the-mueller-report-online-text-of-the-muel... Anne P. Mitchell, Attorney at Law GDPR, CCPA (CA) & CCDPA (CO) Compliance Consultant Author: Section 6 of the CAN-SPAM Act of 2003 (the Federal anti-spam law) Legislative Consultant CEO/President, Institute for Social Internet Public Policy Board of Directors, Denver Internet Exchange Board of Directors, Asilomar Microcomputer Workshop Legal Counsel: The CyberGreen Institute Legal Counsel: The Earth Law Center California Bar Association Cal. Bar Cyberspace Law Committee Colorado Cyber Committee Ret. Professor of Law, Lincoln Law School of San Jose Ret. Chair, Asilomar Microcomputer Workshop
On Apr 18, 2019, at 8:33 AM, Mel Beckman <mel@beckman.org> wrote:
B&N just announced that they are offering free downloads via their Nook reader. I noticed I couldn’t reach B&N via IPv6, and discovered the cause :
nslookup
set type=AAAA barnesandnoble.com Server: 4.2.2.1 Non-authoritative answer: *** Can't find barnesandnoble.com: No answer
set type=A barnesandnoble.com. Server: 4.2.2.1 Non-authoritative answer: Name: barnesandnoble.com Address: 161.221.74.213
I don’t know if this is a temporary DNS failure, or B&N really still has no IPv6 hosted web services :)
-mel
On Apr 18, 2019, at 6:46 AM, Naslund, Steve <SNaslund@medline.com> wrote:
Agreed, I remember the biggest problem when the Starr Report was released was that our dial-up PoPs had all lines busy. It was a different Internet then.
Steven Naslund Chicago IL
Hey Mike.
Agreed. But the scale of a 400 page document with global interest? Should be highly cached with a good ratio of served to pull bits. I'm willing to bet you a beer its just another day on the Internet. However, I could be wrong. Hope to see you in DC to collect! I already know Brett is in. :)
In article <BA8E512D-B31E-473F-830A-62395E7604C1@isipp.com> you write:
Oops..the link would be helpful, sorry!
We have made the full report available here, including conclusions (full report both embedded by iframe, and linked to the actual report at DOJ).
The DOJ web site is hosted on Akamai's CDN. I don't think anyone's had trouble getting to it or downloading the report. I certainly didn't.
Oops..the link would be helpful, sorry!
We have made the full report available here, including conclusions (full report both embedded by iframe, and linked to the actual report at DOJ).
The DOJ web site is hosted on Akamai's CDN. I don't think anyone's had trouble getting to it or downloading the report. I certainly didn't.
However I was responding to someone who couldn't get it from B&N. That said, our reason for making it available at TIP was that a) not everyone knows how to find the DOJ site, and more importantly b) to preserve it if/when the DOJ buries it. Anne Anne P. Mitchell, Attorney at Law GDPR, CCPA (CA) & CCDPA (CO) Compliance Consultant Author: Section 6 of the CAN-SPAM Act of 2003 (the Federal anti-spam law) Legislative Consultant CEO/President, Institute for Social Internet Public Policy Board of Directors, Denver Internet Exchange Board of Directors, Asilomar Microcomputer Workshop Legal Counsel: The CyberGreen Institute Legal Counsel: The Earth Law Center California Bar Association Cal. Bar Cyberspace Law Committee Colorado Cyber Committee Ret. Professor of Law, Lincoln Law School of San Jose Ret. Chair, Asilomar Microcomputer Workshop
I can’t believe p2p isn’t used more, even inside companies. It does have legit uses From: NANOG <nanog-bounces@nanog.org> On Behalf Of Mark Seiden Sent: Wednesday, April 17, 2019 11:27 PM To: fwessling@succinctsystems.com; Mark Tinka via NANOG <nanog@nanog.org> Subject: Re: Special Counsel Office report web site of course p2p is the way to distribute this but i doubt the justice department can admit there is any positive legitimate use for p2p. (i’ve been surprised that it hasn’t made it to wikileaks or bittorrent yet. “russiar, are you listening?”) (i sure hope there’s a signed version or at least a hash.) i predict there will be versions with fake content, missing content, and malware inserted that are distributed as well. and i’ll bet there will be some infected pdf version as well distributed that way. On Apr 17, 2019, 7:57 PM -0700, fwessling--- via NANOG <nanog@nanog.org<mailto:nanog@nanog.org>>, wrote: And we may still see the web stack being the ultimate cause of the delay. Parkinson's law always comes to the rescue:-) More faster and efficient processing architecture, Hyper transport buses, amd-64 Branch prediction. Massively faster storage subsystems and disk arrays, SSD slab caching for hypervisors And some dude with a AJAX framework to serve a PDF bringging the whole thing to a a screeching halt On April 17, 2019 10:35:29 PM EDT, Sean Donelan <sean@donelan.com<mailto:sean@donelan.com>> wrote: On Wed, 17 Apr 2019, Patrick W. Gilmore wrote: Things will probably be easier this time. The Internet has evolved ways of dealing with exactly this problem. (Avi used to call it “slash-dot insurance”, but the idea is the same.) Specifically: Yep, it will be interesting to see where the chokepoints are tommorrow. In 1998, the bandwidth pipes never filled up. The chokepoint was in the TCP and Web stacks. Eventually the Associated Press got a copy of the Starr Report on a CD from a congressional staffer. The press intern running down the street holding a CD was faster than 1998 internet :-) We were also lucky in 1998, no one had thought of DDOS yet. Frederick Wessling (CIO) Succinct Systems LLC Cell: +1(561) 571-2799 Office: +1(904) 758-9915 ext. 9925 Fax: +1(904) 758-9987 www.SuccinctSystems.com<http://www.SuccinctSystems.com>
On Thu, Apr 18, 2019 at 12:56:03PM +0000, Kain, Rebecca (.) wrote:
I can???t believe p2p isn???t used more, even inside companies. It does have legit uses
It does, and some of the use cases for it are quite compelling. However, there is often deep mistrust associated with it: years of propaganda from the copyright lobby have fostered the impression that it is inherently malicious. That can be very difficult to overcome: it's in the same class of mythos as "all ICMP traffic is bad", and well, lots of us have spent lots of time over lots of years trying to get past that one. Getting P2P accepted looks like a much bigger hill to climb. ---rsk
On Wed, Apr 17, 2019 at 09:02:52PM -0400, Sean Donelan wrote:
The Special Counsel's report is expected to be posted [...]
Not quite. A *version* of the report that has been redacted by the President's hand-picked obedient lackey will be posted. I suspect that the full report will find its way to us via other means. ---rsk
Rich, If you want NANOG to devolve into a morass of political claptrap, keep posting comments like that. Personally, I want NANOG to remain a useful technical resource, and leave the partisan crap to Facebook and its ilk. -mel beckman
On Apr 18, 2019, at 7:18 AM, Rich Kulawiec <rsk@gsp.org> wrote:
On Wed, Apr 17, 2019 at 09:02:52PM -0400, Sean Donelan wrote: The Special Counsel's report is expected to be posted [...]
Not quite. A *version* of the report that has been redacted by the President's hand-picked obedient lackey will be posted.
I suspect that the full report will find its way to us via other means.
---rsk
On Wed, 17 Apr 2019, Sean Donelan wrote:
The Special Counsel's report is expected to be posted on its website sometime between 11 a.m. and noon on Thursday, April 18, 2019.
Its been about 7 hours since the report was released on the SCO web site and to the news media. Ignoring the content of the report, and looking only at technical network distribution issues: 1. I did not experience and did not see any reports of network distribution problems. 2. I did not experience and did not see any reports of malicious DDOS or attempts to disrupt the distribution.
On 4/18/2019 3:44 PM, Sean Donelan wrote:
On Wed, 17 Apr 2019, Sean Donelan wrote:
The Special Counsel's report is expected to be posted on its website sometime between 11 a.m. and noon on Thursday, April 18, 2019.
Its been about 7 hours since the report was released on the SCO web site and to the news media. Ignoring the content of the report, and looking only at technical network distribution issues:
1. I did not experience and did not see any reports of network distribution problems.
2. I did not experience and did not see any reports of malicious DDOS or attempts to disrupt the distribution.
I think every news website had a copy: CNN, Fox, Reuters, US Today, MSNBC etc. Even aljazeera.com and BBC News had copies. I don't know anyone who used a .gov website.
participants (17)
-
Anne P. Mitchell, Esq. -
Brett Watson -
fwessling＠succinctsystems.com -
Jared Mauch -
John Levine -
Kain, Rebecca (.) -
Marco Belmonte -
Mark Seiden -
Martin Hannigan -
Mel Beckman -
mike.lyon＠gmail.com -
Naslund, Steve -
Patrick W. Gilmore -
Randy Bush -
Rich Kulawiec -
Roy -
Sean Donelan