The list is not the proper forum for a debate on this topic, and I'm not
trying to start one.
But ask yourself *now* what happens if you get these kinds of orders, so
that you can give a reasoned answer.
https://plus.google.com/+LaurenWeinstein/posts/TYxXkeQ2jPW
Cheers,
-- jra
--
Jay R. Ashw
Not trying to start a debate but let me post a controversial topic that is just
a guess at what someone might do. Yeah, Ok.
Steven Naslund
Chicago IL
-Original Message-
From: NANOG [mailto:nanog-boun...@nanog.org] On Behalf Of Jay R. Ashworth
Sent: Wednesday, November 09, 2016 2:57 PM
To
You're right, this is not the forum. So why are you abusing it?
-mel beckman
> On Nov 9, 2016, at 12:57 PM, Jay R. Ashworth wrote:
>
> The list is not the proper forum for a debate on this topic, and I'm not
> trying to start one.
>
> But ask yourself *now* what happens if you get these kinds
On 11/9/16 2:17 PM, Mel Beckman wrote:
You're right, this is not the forum. So why are you abusing it?
I do think it's a fair thing to drop in everyone's lap though.
Something to think about, and consider, even if privately and to ones self.
--
Brielle Bruns
The Summit Open Source Developme
In message <1624203180.33527.1478724998723.javamail.zim...@baylink.com>,
"Jay R. Ashworth" wrote:
>The list is not the proper forum for a debate on this topic, and I'm not
>trying to start one.
>
>But ask yourself *now* what happens if you get these kinds of orders, so
>that you can give a reas
On Wed, Nov 9, 2016 at 3:56 PM, Jay R. Ashworth wrote:
> But ask yourself *now* what happens if you get these kinds of orders, so
> that you can give a reasoned answer.
>
> https://plus.google.com/+LaurenWeinstein/posts/TYxXkeQ2jPW
Hi Jay,
I think this discussion is premature. We can hypothesi
Hi all,
Please consider our Mail List Charter and Policy: http://nanog.org/list
The NANOG mailing list is established to provide a forum for the
exchange of technical information and the discussion of specific
implementation issues that require cooperation among network service
providers.
In ord
Thank you.
Get Outlook for iOS
On Wed, Nov 9, 2016 at 6:06 PM -0500, "Job Snijders" wrote:
Hi all,
Please consider our Mail List Charter and Policy: http://nanog.org/list
The NANOG mailing list is established to provide a forum for the
exchange of technical information and the di
Apologies if this kind of thing isn't allowed but I'm at the end of my
tether. If anyone who works at OpenSRS lurks here, can you contact me
off-list? I have an issue support is unwilling or unable to fix and they
don't seem too keen on escalating it.
// jkl
Over at Language Hat, they are trying to establish the common
pronunciation of "read receipts" [1]
To me, they've always just been "DSNs" or "MDNs", however, according to
rfc2298, their history goes back further.
Of those who lived that history, and actually heard or said "read
receipts", did you
Greetings Team,
While I haven't worked with IS-IS before but the only disadvantage I've
encountered with OSPF is that it is resource intensive on the router it is
running on which is why only one instance runs on any PE & P device on an
ISP network. OSPF is pretty good in handling the core networ
I avoided the other off charter bait, but this is a red dot to me.
On 11/6/2016 19:59, Patrick wrote:
Over at Language Hat, they are trying to establish the common
pronunciation of "read receipts" [1]
To me, they've always just been "DSNs" or "MDNs", however, according to
rfc2298, their history
vi users prefer ospf
emacs users prefer is-is
randy
On Wed, 9 Nov 2016 17:12:24 +
Michael Bullut wrote:
> Although there isn't distinct 1:1 argument, it's good we discuss it
> here and figure out why one prefer one over the other *(consider a
> huge flat network)**.* What say you ladies and gentlemen?
I'm not sure it is worthy of an argument.
> On Nov 9, 2016, at 6:04 PM, Randy Bush wrote:
>
> vi users prefer ospf
> emacs users prefer is-is
>
So that leaves EIGRP for the nano users?
David Barak
Sent from mobile device, please excuse autocorrection artifacts
>> vi users prefer ospf
>> emacs users prefer is-is
> So that leaves EIGRP for the nano users?
teco
I will definitely be looking up the notes from AOL that John referenced.
But working for a vendor and getting insight from multiple ISPs, here are a
few of the things that I hear most frequently:
1) Network Topology support - The differences between a single OSPF
backbone area and a contiguous set
Vendor support for IS-IS is quite limited - many options for OSPF.
On Nov 9, 2016 8:47 PM, "RT Parrish" wrote:
> I will definitely be looking up the notes from AOL that John referenced.
> But working for a vendor and getting insight from multiple ISPs, here are a
> few of the things that I hear
On 9/Nov/16 19:12, Michael Bullut wrote:
> Greetings Team,
>
> While I haven't worked with IS-IS before but the only disadvantage I've
> encountered with OSPF is that it is resource intensive on the router it is
> running on which is why only one instance runs on any PE & P device on an
> ISP n
And yes, IS-IS not running over IP is also a great thing.
Mark.
On 10/Nov/16 04:27, John Kristoff wrote:
>
> I've considered leaving IPv4 on OSPF and putting IPv6 on IS-IS, but I'm
> not sure it really matters. It might be nice to get the experience on
> the resume, but that might not be a good justification to the network
> staff and management for a produ
On 10/Nov/16 04:45, RT Parrish wrote:
> 1) Network Topology support - The differences between a single OSPF
> backbone area and a contiguous set of Level-2 adjacencies will occasionally
> be a deciding factor.
L2 IS-IS can be as chatty as single-area OSPF. That said, IS-IS has
native tools to r
On 10/Nov/16 04:52, Josh Reynolds wrote:
> Vendor support for IS-IS is quite limited - many options for OSPF.
Depends on the vendor.
Cisco have as many knobs for IS-IS as they do for OSPF.
Juniper, not so much.
Don't know about other vendors.
At any rate, many of these knobs are not part of
This generally supports my own view that it depends on the topology
and the real or potential scale/scope. In my experience, IS-IS is just
all around better in a flat, highly interconnected environment such as
an ISP or other broadly scaled network. If you have a very (almost
exclusively) heirarchi
On 10/Nov/16 08:41, Wayne Bouchard wrote:
> This generally supports my own view that it depends on the topology
> and the real or potential scale/scope. In my experience, IS-IS is just
> all around better in a flat, highly interconnected environment such as
> an ISP or other broadly scaled netwo
25 matches
Mail list logo
