Re: RFC becomes Visio

The newest version of libreoffice draw can open Visio diagrams. --- Brian Raaen Zcorum On Tue, Oct 2, 2012 at 5:43 PM, Michael Hallgren wrote: > Le mardi 02 octobre 2012 à 23:25 +0200, Dan Luedtke a écrit : >> On Fri, 2012-09-28 at 19:31 +0100, Nick Hilliard wrote: >> > Here's a visio diagram yo

Re: RFC becomes Visio

On Oct 3, 2012, at 7:26 AM, Brian Christopher Raaen < mailing-li...@brianraaen.com> wrote: The newest version of libreoffice draw can open Visio diagrams. Also Microsoft does provide a free Visio plugin/viewer for Internet Explorer. http://www.microsoft.com/en-us/download/details.aspx?displayla

Re: RFC becomes Visio

Le mercredi 03 octobre 2012 à 07:31 -0400, Rodrick Brown a écrit : > On Oct 3, 2012, at 7:26 AM, Brian Christopher Raaen > wrote: > > > > The newest version of libreoffice draw can open Visio diagrams. > > > > > > > Also Microsoft does provide a free Visio plugin/viewer for Internet > Explor

Re: Internet routing table "completeness" monitoring?

- Original Message - > From: "ML" > Has anyone put in place a method to identify if one their BGP peers > suddenly withdraws X% of their prefixes? > > e.g I should expect ~420k prefixes in a "complete"[1] routing table from > a transit peer today. If suddenly I'm only getting 390k prefix

RE: Internet routing table "completeness" monitoring?

I have cacti graph the amount of prefixes announced and withdrawn from a BGP peer on each BGP router. -Original Message- From: ML [mailto:m...@kenweb.org] Sent: Tuesday, October 02, 2012 11:43 PM To: North American Networking and Offtopic Gripes List Subject: Internet routing table "co

RE: So what's the deal with 10Gbase-T

It was really unfortunate of Intel to release Romley with 10G copper only support at launch, I hear though that soon there will be motherboards with the SFP+ ports integrated. -Original Message- From: Miquel van Smoorenburg [mailto:mik...@xs4all.net] Sent: Monday, October 01, 2012 5:28

RE: Internet routing table "completeness" monitoring?

I agree, and just use the Threshold plugin so when it drops below or goes above a certain # to notify you. http://docs.cacti.net/plugin:thold -Original Message- From: Joseph Jackson [mailto:jjack...@aninetworks.net] Sent: Wednesday, October 03, 2012 9:51 AM To: m...@kenweb.org; North Ame

RE: Internet routing table "completeness" monitoring?

Not sure I don't have any non-cisco BGP routers. Sorry! -Original Message- From: Neil Robst [mailto:neil.ro...@kit-digital.com] Sent: Wednesday, October 03, 2012 8:54 AM To: Joseph Jackson; m...@kenweb.org; North American Networking and Offtopic Gripes List Subject: RE: Internet routi

RE: Internet routing table "completeness" monitoring?

On Wed, 3 Oct 2012, Joseph Jackson wrote: I have cacti graph the amount of prefixes announced and withdrawn from a BGP peer on each BGP router. +1 Note that not all router OSs support fetching data like that via SNMP. We use a custom built thing internally that does this two, which we then

RE: So what's the deal with 10Gbase-T

Odd wording on the timing; I'm aware of at least one manufactured 1U system with onboard SFP+ that's been available since Q1-Q2 of this year. (I don't work for the manufacturer, just for a fairly happy customer.) Jima On Wed, Oct 3, 2012, at 7:54am, Drew Weaver wrote: > It was really unfo

RE: [j-nsp] Krt queue issues

Look into Static route retain. Should keep the route in the forwarding table. >From Jniper site <<< Route Retention By default, static routes are not retained in the forwarding table when the routing process shuts down. When the routing process starts up again, any routes configured as static r

Re: Internet routing table "completeness" monitoring?

On Wed, Oct 3, 2012 at 9:55 AM, Eric Tykwinski wrote: > I agree, and just use the Threshold plugin so when it drops below or goes > above a certain # to notify you. > http://docs.cacti.net/plugin:thold is a threshold helpful here? (well, it's helpful to a point at least) what if your neighbour st

Re: Internet routing table "completeness" monitoring?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 10/3/2012 10:16 AM, William F. Maton Sotomayor wrote: > On Wed, 3 Oct 2012, Joseph Jackson wrote: > >> I have cacti graph the amount of prefixes announced and withdrawn from a BGP peer on each BGP router. > > +1 > > Note that not all router OSs su

IPv4 address length technical design

Is anyone aware of any historical documentation relating to the choice of 32 bits for an IPv4 address? Cheers.

Re: IPv4 address length technical design

On Wed, Oct 3, 2012 at 12:13 PM, Chris Campbell wrote: > Is anyone aware of any historical documentation relating to the choice of 32 > bits for an IPv4 address? > > Cheers. I believe the relevant RFC is RFC 791 - https://tools.ietf.org/html/rfc791 -- Sadiq S O< ascii ribbon campaign - stop ht

Re: IPv4 address length technical design

I'll add that in the mid-90's, in a University Of Washington lecture hall, Vint Cerf expressed some regret over going with 32 bits. Chuckle worthy and at the time, and a fond memory - K Sadiq Saif wrote: >On Wed, Oct 3, 2012 at 12:13 PM, Chris Campbell >wrote: >> Is anyone aware of any histo

Re: IPv4 address length technical design

Op 3-10-2012 18:33, Kevin Broderick schreef: I'll add that in the mid-90's, in a University Of Washington lecture hall, Vint Cerf expressed some regret over going with 32 bits. Chuckle worthy and at the time, and a fond memory - K "Pick a number between this and that." It's the 80's and you

Re: IPv4 address length technical design

Chris Campbell writes: > Is anyone aware of any historical documentation relating to the choice of 32 > bits for an IPv4 address? > > Cheers. 8 bit host identifiers had proven to be too short... :) -r

Re: Internet routing table "completeness" monitoring?

On Wed, 3 Oct 2012, Christopher Morrow wrote: is a threshold helpful here? (well, it's helpful to a point at least) what if your neighbour starts deaggragating (or sending you their internal deaggragates) in place of 50k real routes? no alarm, no 'change' from a numbers perspective, but certainl

RE: IPv4 address length technical design

> Sadiq Saif [mailto:sa...@asininetech.com] wrote: > > On Wed, Oct 3, 2012 at 12:13 PM, Chris Campbell > wrote: > > Is anyone aware of any historical documentation relating to the choice of 32 > bits for an IPv4 address? > > > > Cheers. > > I believe the relevant RFC is RFC 791 - https://tools.ie

Re: IPv4 address length technical design

On Wed, Oct 03, 2012 at 06:52:57PM +0200, Seth Mos wrote: > "Pick a number between this and that." It's the 80's and you can > still count the computers in the world. :) And yet, almost concurrently, IEEE 802 went with forty-eight bits. Go figure. I'm pretty sure the explanation you're looking f

Re: IPv4 address length technical design

On Wed, Oct 3, 2012 at 12:11 PM, Tony Hain wrote: >> Sadiq Saif [mailto:sa...@asininetech.com] wrote: >> >> On Wed, Oct 3, 2012 at 12:13 PM, Chris Campbell >> wrote: >> > Is anyone aware of any historical documentation relating to the choice of >> > 32 >> bits for an IPv4 address? >> > >> > Chee

Re: IPv4 address length technical design

On Wed, Oct 3, 2012 at 12:22 PM, Izaac wrote: > On Wed, Oct 03, 2012 at 06:52:57PM +0200, Seth Mos wrote: >> "Pick a number between this and that." It's the 80's and you can >> still count the computers in the world. :) > > And yet, almost concurrently, IEEE 802 went with forty-eight bits. Go > f

RE: IPv4 address length technical design

Perhaps worth noting (for the archives) that a significant part of the early ARPAnet was DECsystem-10's with 36-bit words. http://en.wikipedia.org/wiki/PDP-10 http://en.wikipedia.org/wiki/Email Tony Patti CIO S. Walter Packaging Corp. -Original Message- From: George Herbert [mailto:ge

Re: IPv4 address length technical design

On Wed, 03 Oct 2012 15:44:16 -0400, "Tony Patti" said: > > Perhaps worth noting (for the archives) that a significant part of the early > ARPAnet was DECsystem-10's with 36-bit words. And the -10s and -20s were the major reason RFCs refer to octets rather than bytes, as they had a rather slippery

Re: IPv4 address length technical design

On Wed, Oct 3, 2012 at 3:22 PM, Izaac wrote: > On Wed, Oct 03, 2012 at 06:52:57PM +0200, Seth Mos wrote: >> "Pick a number between this and that." It's the 80's and you can >> still count the computers in the world. :) > > And yet, almost concurrently, IEEE 802 went with forty-eight bits. Go > fi

Re: IPv4 address length technical design

Is anyone aware of any historical documentation relating to the choice of 32 bits for an IPv4 address? ... Actually that was preceded by RFC 760, which in turn was a derivative of IEN 123. I believe the answer to the original question is ... My theory is that there is a meta-rule to make n

Re: IPv4 address length technical design

- Original Message - > From: "Dave Crocker" > My theory is that there is a meta-rule to make new address spaces have > 4 times as many bits as the previous generation. > > We have three data points to establish this for the Internet, and > that's the minimum needed to run a correlation:

Re: IPv4 address length technical design

--- j...@baylink.com wrote: From: Jay Ashworth So the address space for IPv8 will be... - Jim says: "IPv8 - 43 bits (3+8+32) There is a natural routing hierarchy with IPv8 addressing8 regions, 256 distribution centers in each region and f

Re: IPv4 address length technical design

On Wed, Oct 3, 2012 at 2:19 PM, Scott Weeks wrote: > > > --- j...@baylink.com wrote: > From: Jay Ashworth > > So the address space for IPv8 will be... > > - > > > Jim says: > > "IPv8 - 43 bits (3+8+32) > > There is a natural routing hierarchy with

RE: IPv4 address length technical design

Remember that at the time, IP was designed to be classful so having four 8 bit bytes was real convenient to look only at the bytes in the host portion of the address. Class A meant three significant bytes, Class B had two significant bytes, and Class C had three significant bytes as far as the

RE: [j-nsp] Krt queue issues

I think route retention might help in the event the table was cleared or routing process restarted but I don't that it will help with a boot because the table structures are being built as part of the system initialization. In reality, I would expect the static routes to get installed very early a

Re: IPv4 address length technical design

On Oct 3, 2012, at 12:22 PM, Izaac wrote: > On Wed, Oct 03, 2012 at 06:52:57PM +0200, Seth Mos wrote: >> "Pick a number between this and that." It's the 80's and you can >> still count the computers in the world. :) > > And yet, almost concurrently, IEEE 802 went with forty-eight bits. Go > fi

Rogers.ca fiber contact

Have a fiber circuit that is getting inconsistent speeds to the net L Need an IPERF test on rogers network to verify bandwidth. Dennis Burgess, Mikrotik Certified Trainer Author of "Learn RouterOS- Second Edition " Link Technologies, In

Re: IPv4 address length technical design

On 10/3/12, Jay Ashworth wrote: > So the address space for IPv8 will be... > In 100 years, when we start to run out of IPv6 addresses, possibly we will have learned our lesson and done two things: (1) Stopped mixing the Host identification and the Network identification into the same bit

Re: IPv4 address length technical design

On Wed, 03 Oct 2012 17:49:56 -0500, Jimmy Hess said: > (1) Stopped mixing the Host identification and the Network > identification into the same bit field; instead every packet gets a > source network address, destination network address, AND an > additional tuple of Source host a

Re: IPv4 address length technical design

On Oct 3, 2012, at 3:59 PM, valdis.kletni...@vt.edu wrote: > On Wed, 03 Oct 2012 17:49:56 -0500, Jimmy Hess said: >> (1) Stopped mixing the Host identification and the Network >> identification into the same bit field; > > Where's Noel Chiappa when you need him? Saying "I told you so" I suspe

Re: IPv4 address length technical design

On Oct 3, 2012, at 4:17 PM, Dave Crocker wrote: Is anyone aware of any historical documentation relating to the choice of 32 >>> bits for an IPv4 address? > ... >> Actually that was preceded by RFC 760, which in turn was a derivative >> of IEN 123. I believe the answer to the original qu

Re: IPv4 address length technical design

On Oct 3, 2012, at 6:49 PM, Jimmy Hess wrote: > On 10/3/12, Jay Ashworth wrote: >> So the address space for IPv8 will be... >> > > In 100 years, when we start to run out of IPv6 addresses, possibly we > will have learned our lesson and done two things: > > (1) Stopped mixing the Host ide

Re: IPv4 address length technical design

On Oct 3, 2012, at 3:49 PM, Jimmy Hess wrote: > On 10/3/12, Jay Ashworth wrote: >> So the address space for IPv8 will be... >> > > In 100 years, when we start to run out of IPv6 addresses, possibly we > will have learned our lesson and done two things: > > (1) Stopped mixing the Host i

Re: IPv4 address length technical design

On Wed, Oct 3, 2012 at 4:15 PM, Owen DeLong wrote: > > On Oct 3, 2012, at 3:49 PM, Jimmy Hess wrote: > >> On 10/3/12, Jay Ashworth wrote: >>> So the address space for IPv8 will be... >>> >> >> In 100 years, when we start to run out of IPv6 addresses, possibly we >> will have learned our lesson

Re: IPv4 address length technical design

On October 3, 2012 at 17:09 j...@baylink.com (Jay Ashworth) wrote: > > So the address space for IPv8 will be... > Variable. -b

Re: IPv4 address length technical design

On Wed, Oct 03, 2012 at 06:59:20PM -0400, valdis.kletni...@vt.edu wrote: > Where's Noel Chiappa when you need him? > > > (2) The new protocol will use variable-length address for the Host > > portion, such as used in the addresses of CLNP, > > This also was considered during the IPv6 design