* Jared Mauch:
> Solving a local attack is something I consider different in scope
> than the current draft being discussed in 6man, v6ops, ipv6@ etc...
That's not going to happen because it's a layering violation between
the IETF and IEEE. It has not been solved during thirty years of IPv4
over
* Larry Stites:
> Given what you know now, if you were 21 and just starting into
> networking / communications industry which areas of study or
> specialty would you prioritize?
Law.
_
NANOG mailing list
NANOG@nanog.org
https://mailman.nanog.org/mailman/listinfo/nanog
On Jul 15, 2011, at 10:24 AM, Jimmy Hess wrote:
> In most cases if you have a DoS attack coming from the same Layer-2 network
> that a router is attached to,
> it would mean there was already a serious security incident that occured to
> give the attacker that special point to attack fr
This s
On Jul 17, 2011, at 4:15 PM, Florian Weimer wrote:
> In practice, the IPv4 vs IPv6 difference is that some vendors provide DHCP
> snooping, private VLANs and unicast flood protection in IPv4
> land, which seems to provide a scalable way to build Ethernet networks with
> address validation---but
On Sun, 17 Jul 2011, Florian Weimer wrote:
> In practice, the IPv4 vs IPv6 difference is that some vendors provide
> DHCP snooping, private VLANs and unicast flood protection in IPv4 land,
> which seems to provide a scalable way to build Ethernet networks with
> address validation---but there i
* Mikael Abrahamsson:
> On Sun, 17 Jul 2011, Florian Weimer wrote:
>
>> In practice, the IPv4 vs IPv6 difference is that some vendors
>> provide DHCP snooping, private VLANs and unicast flood protection in
>> IPv4 land, which seems to provide a scalable way to build Ethernet
>> networks with addre
On Sun, 17 Jul 2011, Florian Weimer wrote:
> Others use tunnels, PPPoE or lots of scripting, so certainly something
> can be done about it. To my knowledge, SAVI SEND is still at a similar
> stage. Pointers to vendor documentation would be appreciated if this is
> not the case.
--
Mikael
* Mikael Abrahamsson:
> On Sun, 17 Jul 2011, Florian Weimer wrote:
>
>> Others use tunnels, PPPoE or lots of scripting, so certainly
>> something can be done about it. To my knowledge, SAVI SEND is still
>> at a similar stage. Pointers to vendor documentation would be
>> appreciated if this is n
On Sun, 17 Jul 2011, Florian Weimer wrote:
> Interesting, thnaks. It's not the vendors I would expect, and it's not
> based on SEND (which is not surprising at all and actually a good
> thing).
Personally I think SEND is never going to get any traction.
> Is this actually secure in the sense
* Mikael Abrahamsson:
> On Sun, 17 Jul 2011, Florian Weimer wrote:
>
>> Interesting, thnaks. It's not the vendors I would expect, and it's
>> not based on SEND (which is not surprising at all and actually a
>> good thing).
>
> Personally I think SEND is never going to get any traction.
Last time
_
NANOG mailing list
NANOG@nanog.org
https://mailman.nanog.org/mailman/listinfo/nanog
We all make mistakes in not questioning our own positions, from time to
time. You, Jeff, seem to be making that very same mistake.
Please keep these points in mind:
* Rome wasn't built in a day. The current system didn't come
ready-made pre-built with all the bells and whistles you are us
On Mon, Jul 11, 2011 at 8:17 PM, Karl Auer wrote:
> RFC3756 IPv6 Neighbor Discovery (ND) Trust Models and Threats
>
> In this attack, the attacking node begins fabricating addresses with
> the subnet prefix and continuously sending packets to them. The last
> hop router is obligated to reso
On Sun, Jul 17, 2011 at 11:42 AM, William Herrin wrote:
> My off-the-cuff naive solution to this problem would be to discard the
> oldest incomplete solicitation to fit the new one and, upon receiving
> an apparently unsolicited response to a discarded solicitation,
> restart the process flagging
On Sun, Jul 17, 2011 at 11:07 AM, Eliot Lear wrote:
> We all make mistakes in not questioning our own positions, from time to
> time. You, Jeff, seem to be making that very same mistake.
> Rome wasn't built in a day. The current system didn't come ready-made
> pre-built with all the bells and w
On Jul 17, 2011, at 10:35 AM, Jeff Wheeler wrote:
> On Sun, Jul 17, 2011 at 11:42 AM, William Herrin wrote:
>> My off-the-cuff naive solution to this problem would be to discard the
>> oldest incomplete solicitation to fit the new one and, upon receiving
>> an apparently unsolicited response to
On Sun, Jul 17, 2011 at 3:40 PM, Owen DeLong wrote:
> Basically an ND entry would have the following states and timers:
I've discussed what you have described with some colleagues in the
past. The idea has merit and I would certainly not complain if
vendors included it (as a knob) on their boxes
On Sun, Jul 17, 2011 at 1:35 PM, Jeff Wheeler wrote:
> On Sun, Jul 17, 2011 at 11:42 AM, William Herrin wrote:
>> My off-the-cuff naive solution to this problem would be to discard the
>> oldest incomplete solicitation to fit the new one and, upon receiving
>> an apparently unsolicited response t
On Jul 17, 2011, at 1:17 PM, Jeff Wheeler wrote:
> On Sun, Jul 17, 2011 at 3:40 PM, Owen DeLong wrote:
>> Basically an ND entry would have the following states and timers:
>
> I've discussed what you have described with some colleagues in the
> past. The idea has merit and I would certainly no
On Jul 17, 2011, at 1:32 PM, William Herrin wrote:
> On Sun, Jul 17, 2011 at 1:35 PM, Jeff Wheeler wrote:
>> On Sun, Jul 17, 2011 at 11:42 AM, William Herrin wrote:
>>> My off-the-cuff naive solution to this problem would be to discard the
>>> oldest incomplete solicitation to fit the new one a
There appears to be a login issue at Netflix. Calls to their 1-866-579-7113
number only yields a recording that they are experiencing a higher than normal
call volume, try again later. Widespread?
Robert D. Scott rob...@ufl.edu
Senior Network Engineer 352-273-0113 Phone
CNS - Network
I am unable to login as well.
2011/7/17 Scott, Robert D.
> There appears to be a login issue at Netflix. Calls to their
> 1-866-579-7113 number only yields a recording that they are experiencing a
> higher than normal call volume, try again later. Widespread?
>
> Robert D. Scott rob..
Ipad app says "Service Temporarily Unavailable" at the moment.
Netflix claims to be operating about 90% of their services out of aws and the
only issue on the aws status page is a vpn end point issue from yesterday.
-Original Message-
From: "Scott, Robert D."
Date: Sun, 17 Jul 2011 22
Unreachable from eastern Canada as well
2011/7/17 :
> Ipad app says "Service Temporarily Unavailable" at the moment.
>
> Netflix claims to be operating about 90% of their services out of aws and the
> only issue on the aws status page is a vpn end point issue from yesterday.
>
> -Original Me
On 7/17/2011 12:36 PM, Scott, Robert D. wrote:
> There appears to be a login issue at Netflix. Calls to their 1-866-579-7113
> number only yields a recording that they are experiencing a higher than
> normal call volume, try again later. Widespread?
Likewise from Hawaii. Guess this'll be anot
On 7/17/2011 6:36 PM, Scott, Robert D. wrote:
> There appears to be a login issue at Netflix.
Streaming works here.
Andrew
_
NANOG mailing list
NANOG@nanog.org
https://mailman.nanog.org/mailman/listinfo/nanog
We our designing a new hosted exchange environment as well as Multi-Tenant
Desktop as a Service environment and we are going to use IPv6 public address.
Cheers
Ryan
-Original Message-
From: James Harr [mailto:james.h...@gmail.com]
Sent: Wednesday, July 13, 2011 11:22 AM
To: Joel Maslak
27 matches
Mail list logo
