From ralph@istop.com Tue Dec 10 13:31:26 2002 Received: from someone claiming to be ns.istop.com puck.NOSPAM (ns.istop.com [66.11.168.199]) by puck.nether.net (8.12.6/8.12.6) with ESMTP id gBAIVQph011163 for ; Tue, 10 Dec 2002 13:31:26 -0500 Received: from localhost (localhost [127.0.0.1]) by ns.istop.com (Postfix) with ESMTP id EEF72173AA for ; Tue, 10 Dec 2002 13:32:14 -0500 (EST) Date: Tue, 10 Dec 2002 13:32:14 -0500 (EST) From: Ralph Doncaster To: inet-ops@puck.nether.net Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: [Inet-ops] cheap route server Sender: inet-ops-admin@puck.nether.net Errors-To: inet-ops-admin@puck.nether.net X-BeenThere: inet-ops@puck.nether.net X-Mailman-Version: 2.0.13 Precedence: bulk List-Unsubscribe: , List-Id: list for internet operators List-Post: List-Help: List-Subscribe: , List-Archive: I'm looking for a suggestion for cheap route-servers. Preferably something in the 1-3U size range. I need to be able to take at least 4 full BGP views. And I'd like to spend less than $1500 (used is OK). I've seen some cheap used 7500's that would be OK if they weren't so large. I've been playing with Zebra (0.93b) and it seems to have problems sometimes talking to other routers running Zebra (but talking to Cisco and Juniper seems fine). Anyone used ZebOS? http://www.ipinfusion.com/products/products_home.html Anyone know how it differs from the free version of Zebra? Ralph Doncaster principal, IStop.com From jared Wed Dec 11 00:40:11 2002 Received: (from jared@localhost) by puck.nether.net (8.12.6/8.12.6) id gBB5eBs5016612 for inet-ops@puck.nether.net; Wed, 11 Dec 2002 00:40:11 -0500 Date: Wed, 11 Dec 2002 00:40:11 -0500 From: Jared Mauch To: inet-ops@puck.nether.net Message-ID: <20021211054011.GA16587@puck.nether.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4i Subject: [Inet-ops] test X-BeenThere: inet-ops@puck.nether.net X-Mailman-Version: 2.1b6 Precedence: list List-Id: list for internet operators List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Dec 2002 05:40:11 -0000 ignore. test of new list software. -- Jared Mauch | pgp key available via finger from jared@puck.nether.net clue++; | http://puck.nether.net/~jared/ My statements are only mine. From jared Fri Dec 13 01:13:47 2002 Received: (from jared@localhost) by puck.nether.net (8.12.6/8.12.6) id gBD6Dlvq027789 for inet-ops@puck.nether.net; Fri, 13 Dec 2002 01:13:47 -0500 Resent-Message-Id: <200212130613.gBD6Dlvq027789@puck.nether.net> Received: from someone claiming to be pro1.send24pro4548.com puck.NOSPAM (pro1.send24pro4548.com [64.14.206.179]) by puck.nether.net (8.12.6/8.12.6) with ESMTP id gBD5hlux025646 for ; Fri, 13 Dec 2002 00:43:47 -0500 Received: from [10.0.1.15] by pro1.send24pro4548.com (10.0.1.33) with QMQP; 13 Dec 2002 01:46:12 +0000 Message-Id: <1q1i8q$4tf8ok@pro1.send24pro4548.com> To: jared@nether.net Date: Thu, 12 Dec 2002 19:22:00 -0800 From: connect this holiday MIME-Version: 1.0 X-Mailer-Version: v 13244834 Content-type: text/plain X-Spam-Status: Yes, hits=13.2 required=4.5 tests=CTYPE_JUST_HTML,FROM_ENDS_IN_NUMS,HTML_FONT_COLOR_GRAY, HTML_TAG_BALANCE_HTML,HTML_TAG_EXISTS_TBODY, HTML_TAG_MIXED_CASE,OFFER,RESISTANCE_IS_FUTILE, TO_LEGACY_DOMAIN,WEB_BUGS version=2.50-cvs X-Spam-Flag: YES X-Spam-Level: ************* X-Spam-Checker-Version: SpamAssassin 2.50-cvs (1.127-2002-09-26-exp) X-Spam-Prev-Content-Type: text/html Resent-From: jared@puck.nether.net Resent-Date: Fri, 13 Dec 2002 01:13:47 -0500 Resent-To: inet-ops@puck.nether.net Subject: [Inet-ops] *****SPAM***** 250 business cards ... freee X-BeenThere: inet-ops@puck.nether.net X-Mailman-Version: 2.1b6 Precedence: list Reply-To: bsw32@send24pro4548.com List-Id: list for internet operators List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Dec 2002 06:13:48 -0000 SPAM: -------------------- Start SpamAssassin results ---------------------- SPAM: This mail is probably spam. The original message has been altered SPAM: so you can recognise or block similar unwanted mail in future. SPAM: See http://spamassassin.org/tag/ for more details. SPAM: SPAM: Content analysis details: (13.20 hits, 4.5 required) SPAM: TO_LEGACY_DOMAIN (2.5 points) To: specfies old system (nether.net) SPAM: FROM_ENDS_IN_NUMS (0.9 points) From: ends in numbers SPAM: RESISTANCE_IS_FUTILE (0.7 points) BODY: Resistance to this spam is futile SPAM: OFFER (0.7 points) BODY: Free Offer SPAM: HTML_TAG_EXISTS_TBODY (1.0 points) BODY: HTML has "tbody" tag SPAM: HTML_TAG_BALANCE_HTML (1.0 points) BODY: HTML has unbalanced "html" tags SPAM: HTML_FONT_COLOR_GRAY (0.3 points) BODY: HTML font color is gray SPAM: WEB_BUGS (0.1 points) BODY: Image tag with an ID code to identify you SPAM: HTML_TAG_MIXED_CASE (1.0 points) RAW: HTML tags are inconsistently capitalized SPAM: CTYPE_JUST_HTML (5.0 points) HTML-only mail, with no text version SPAM: SPAM: -------------------- End of SpamAssassin results ---------------------
You are receiving this exclusive promotion from AdPro Solutions as part of the terms of service agreed to when you signed up with AdPro Solutions through one of its network of affiliate sites. Replying to this email will not unsubscribe you. Please follow the instructions at the end of this message if you would prefer not to receive these special offers in the future.

To discontinue the receipt of emails, visit the following linkhttp://rem2.send24pro4548.com/cgi-bin/oaun.cgi?email=jared@nether.net


From 593ittabkg@famouslukes.us Tue Sep 23 15:35:27 2003 Received: from someone claiming to be phat.nether.net puck.NOSPAM (phat.nether.net [IPv6:3ffe:a00:f:4::2]) by puck.nether.net (8.12.10/8.12.9) with ESMTP id h8NJZQSU013258; Tue, 23 Sep 2003 15:35:26 -0400 Received: from someone claiming to be as5300-s26-149.cnt.entelchile.net PhAT.NOSPAM (as5300-s26-149.cnt.entelchile.net [164.77.124.159] (may be forged)) by phat.nether.net (8.12.10/8.11.2) with SMTP id h8NJXAPj027199; Tue, 23 Sep 2003 19:33:14 GMT Message-ID: <0rnk4gl52ci1m93xt4@b1z.gz.nl.z1r> From: "Saundra Tolbert" <593ittabkg@famouslukes.us> To: inet-ops@puck.nether.net Date: Tue, 23 Sep 2003 22:25:54 +0500 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="F3EF.E__A.3." Cc: irtf-rr@puck.nether.net, majdi@puck.nether.net, foundry-nsp@puck.nether.net, jiffer@puck.nether.net, sysmon-announce@puck.nether.net, cisco-nsp@puck.nether.net Subject: [inet-ops] Isn't it time bifjlvlxgctsfcc X-BeenThere: inet-ops@puck.nether.net X-Mailman-Version: 2.1.2 Precedence: list Reply-To: Saundra Tolbert <593ittabkg@famouslukes.us> List-Id: list for internet operators List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Sep 2003 19:35:28 -0000 --F3EF.E__A.3. Content-Type: text/html; Content-Transfer-Encoding: quoted-printable

As Seen on NBC, CBS,
CNN and even Oprah!


The Health Discovery that Actually Reverses Aging while Burning Fat,
without Dieting or Exercise!

This Proven Discovery has even been reported
on by the New England Journal of Medicine.

Forget Aging and Dieting Forever!

And it's Guaranteed!

Free Shipping within the US!

Click Here to Learn How You can Receive up to 2 Full
Month's Supplies Absolutely FREE!

Would you like to lose weight while you sleep?

No dieting!
No hunger pains!
No Cravings!
No strenuous exercise!

Change Your Life Forever!

1. Body Fat Loss..................82% improvement.
2. Wrinkle Reduction.............61% improvement.
3. Energy Level.....................84% improvement.
4. Muscle Strength................88% improvement.
5. Sexual Potency.................75% improvement.
6. Emotional Stability.............67% improvement.
7. Memory.............................62% improvement.

Get Your FREE 2 Month Supply TODAY!
FREE "Eat Until You're Thin Program"
Eat All You Want and Lose Up To 15 Pounds
in One to Two Weeks

You are receiving this message as a member of the Opt-In
America List. To remove your email address please
click here
We honor all remove requests.

zqpugetkb ciehre ri nqhsz qyo zwc jb jup j eflu plnnddi rafqr --F3EF.E__A.3.-- From lwb85fjpc@fabulouslarrys.net Fri Sep 26 15:41:32 2003 Received: from someone claiming to be dsl-200-67-223-185.prodigy.net.mx puck.NOSPAM (dsl-200-67-223-185.prodigy.net.mx [200.67.223.185]) by puck.nether.net (8.12.10/8.12.9) with SMTP id h8QJfPYf013184; Fri, 26 Sep 2003 15:41:30 -0400 (envelope-from lwb85fjpc@fabulouslarrys.net) Message-ID: From: "Alexandria Conner" To: foundry-nsp@puck.nether.net Date: Fri, 26 Sep 2003 18:27:54 +0100 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="D76EB_38E197_1BEE98.ABE" Cc: irtf-rr@puck.nether.net, jiffer@puck.nether.net, inet-ops@puck.nether.net Subject: [inet-ops] that jennifer Anniston.... hmboj X-BeenThere: inet-ops@puck.nether.net X-Mailman-Version: 2.1.2+ Precedence: list Reply-To: Alexandria Conner List-Id: list for internet operators List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Sep 2003 19:41:33 -0000 --D76EB_38E197_1BEE98.ABE Content-Type: text/html; Content-Transfer-Encoding: quoted-printable

As Seen on NBC, CBS,
CNN and even Oprah!


The Health Discovery that Actually Reverses Aging while Burning Fat,
without Dieting or Exercise!

This Proven Discovery has even been reported
on by the New England Journal of Medicine.

Forget Aging and Dieting Forever!

And it's Guaranteed!

Free Shipping within the US!

Click Here to Learn How You can Receive up to 2 Full
Month's Supplies Absolutely FREE!

Would you like to lose weight while you sleep?

No dieting!
No hunger pains!
No Cravings!
No strenuous exercise!

Change Your Life Forever!

1. Body Fat Loss..................82% improvement.
2. Wrinkle Reduction.............61% improvement.
3. Energy Level.....................84% improvement.
4. Muscle Strength................88% improvement.
5. Sexual Potency.................75% improvement.
6. Emotional Stability.............67% improvement.
7. Memory.............................62% improvement.

Get Your FREE 2 Month Supply TODAY!
FREE "Eat Until You're Thin Program"
Eat All You Want and Lose Up To 15 Pounds
in One to Two Weeks

You are receiving this message as a member of the Opt-In
America List. To remove your email address please
click here
We honor all remove requests.

bkjj uitm --D76EB_38E197_1BEE98.ABE-- From davispaul@shuf.com Fri Oct 3 18:32:51 2003 Received: from someone claiming to be ok61664.com puck.NOSPAM (80.179.101.206.forward.012.net.il [80.179.101.206]) by puck.nether.net (8.12.10/8.12.9) with SMTP id h93MWeav016623 for ; Fri, 3 Oct 2003 18:32:44 -0400 (envelope-from davispaul@shuf.com) Message-Id: <200310032232.h93MWeav016623@puck.nether.net> From: "DAVIS YOGA PAUL" To: inet-ops@puck.nether.net Date: Fri, 3 Oct 2003 23:30:26 +0100 X-Mailer: Microsoft Outlook Express 5.00.2919.6900 DM MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by puck.nether.net id h93MWeav016623 Subject: [inet-ops] BANK X-BeenThere: inet-ops@puck.nether.net X-Mailman-Version: 2.1.2+ Precedence: list Reply-To: davispaul@shuf.com List-Id: list for internet operators List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Oct 2003 22:32:51 -0000 HEADQUARTERSPLOT 84 AJOSE ADEOGUN STREET VICTORIA ISLAND LAGOS ATTN:Sir/Ma, STRICTLY A PRIVATE BUSINESS PROPOSAL I am Dr.Davis.Yoga.Paul,a manager in the Bills and Exchange at the Foreign Remittance Department of the ZENITH INTERNATIONAL BANK I am writing this letter to ask for your support and cooperation to carry out this business opportunity in my department. We discovered an abandoned sum of$15,000,000.00 (Fifteen million United States Dollars only) in an account that belongs to one of our foreign customers who died along with his entire family of a wife and two children in November 1997 in a Plane crash.Since we heard of his death, we have been expecting his next-of-kin to come over and put claims for his money as the heir, because we cannot release the fund from his account unless someone applies for claim as the next-of-kin to the deceased as indicated in our banking guidelines.Unfortunately, neither their family member nor distant relative has everappeared to claim the said fund. Upon this discovery, I and other officials in my department have agreed to make business with you and release the total amount into your account as the heir of the fund since no one came for it ordiscovered he maintained account with our bank, otherwise the fund will be returned to the banks treasury as unclaimed fund.We have agreed that our ratio of sharing will be as stated thus;20 % for you as foreign partner,75 % for us the officials in my department and 5 % for the settlement of all local and foreign expences incurred by us and you during the course of this business.Upon the successful completion of this transfer, I and one of my colleagues will come to your country and mind our share. It is from our 75 % we intend to import Agricultural Machineries into my country as a way of recycling the fund. To commence this transaction, we require you to immediately indicate your interest by a return e-mail and enclose your private contact telephone number, fax number full name and address and your designated bank coordinates to enable us file letter of claim to the appropriate departments for necessary approvals before the transfer can be made.Note also, this transaction must be kept STRICTLY CONFIDENTIAL because of its nature. I look forward to receiving your prompt response. Alternative / Email Addres :davispaul@shuf.com DR.Davis.Yoga.Paul From vdekeyzer@mactelecom.com Thu Oct 16 07:42:47 2003 Received: from someone claiming to be quattrostagioni.mactelecom.net puck.NOSPAM (yellow.mactelecom.net [217.64.240.18] (may be forged)) by puck.nether.net (8.12.10/8.12.9) with ESMTP id h9GBgka3008592 for ; Thu, 16 Oct 2003 07:42:47 -0400 (envelope-from vdekeyzer@mactelecom.com) Received: from star_academy.office.mactelecom.com (MAC-01.mactelecom.net [217.64.240.6]) by quattrostagioni.mactelecom.net (Postfix) with ESMTP id 1B8CE5B4A7 for ; Thu, 16 Oct 2003 14:38:44 +0200 (CEST) Received: by star_academy.office.mactelecom.com with Internet Mail Service (5.5.2653.19) id <49FYBBMM>; Thu, 16 Oct 2003 13:39:59 +0200 Message-ID: <0A89B09D5909F94A96C5480667C6BE8912E36A@star_academy.office.mactelecom.com> From: Vincent De Keyzer To: "'inet-ops@puck.nether.net'" Date: Thu, 16 Oct 2003 13:39:49 +0200 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C393DA.34E8A000" Subject: [inet-ops] Anti-spam policy X-BeenThere: inet-ops@puck.nether.net X-Mailman-Version: 2.1.3 Precedence: list List-Id: list for internet operators List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Oct 2003 11:42:48 -0000 This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01C393DA.34E8A000 Content-Type: text/plain Hi, I see some spam e-mails delivered to my customers via my MX which is a backup for them... it seems that for some reason, they trust me more than the average Internet SMTP client. So I am wondering what should be good practice against spam. Should I: 1) leave it like that and let the customer decide on his anti-spam policy 2) apply some anti-spam on my MX; at the risk of rejecting valid e-mail? V PS: hoping there is still somebody listening to this list... ------_=_NextPart_001_01C393DA.34E8A000 Content-Type: text/html Message
Hi,
 
I see some spam e-mails delivered to my customers via my MX which is a backup for them... it seems that for some reason, they trust me more than the average Internet SMTP client.
 
So I am wondering what should be good practice against spam. Should I:
1) leave it like that and let the customer decide on his anti-spam policy
2) apply some anti-spam on my MX; at the risk of rejecting valid e-mail?
 
V
 
PS: hoping there is still somebody listening to this list...
 
------_=_NextPart_001_01C393DA.34E8A000-- From cboyd@gizmopartners.com Thu Oct 16 10:40:46 2003 Received: from someone claiming to be ms-smtp-05.texas.rr.com puck.NOSPAM (ms-smtp-05.texas.rr.com [24.93.36.233]) by puck.nether.net (8.12.10/8.12.9) with ESMTP id h9GEeka3026386 for ; Thu, 16 Oct 2003 10:40:46 -0400 (envelope-from cboyd@gizmopartners.com) Received: from gizmopartners.com (cs24359-109.austin.rr.com [24.243.59.109]) by ms-smtp-05.texas.rr.com (8.12.10/8.12.2) with ESMTP id h9GEGOu5013704; Thu, 16 Oct 2003 09:16:26 -0500 (CDT) Date: Thu, 16 Oct 2003 09:40:42 -0500 Subject: Re: [inet-ops] Anti-spam policy Content-Type: text/plain; charset=ISO-8859-1; format=flowed Mime-Version: 1.0 (Apple Message framework v552) To: Vincent De Keyzer From: Chris Boyd In-Reply-To: <0A89B09D5909F94A96C5480667C6BE8912E36A@star_academy.office.mactelecom.com> Message-Id: X-Mailer: Apple Mail (2.552) Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by puck.nether.net id h9GEeka3026386 Cc: "'inet-ops@puck.nether.net'" X-BeenThere: inet-ops@puck.nether.net X-Mailman-Version: 2.1.3 Precedence: list List-Id: list for internet operators List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Oct 2003 14:40:47 -0000 On Thursday, October 16, 2003, at 06:39 AM, Vincent De Keyzer wrote: > Hi, >   > I see some spam e-mails delivered to my customers via my MX which is a > backup for them... it seems that for some reason, they trust me more > than the average Internet SMTP client. >   > So I am wondering what should be good practice against spam. Should I: > 1) leave it like that and let the customer decide on his anti-spam > policy > 2) apply some anti-spam on my MX; at the risk of rejecting valid > e-mail? >   > V >   > PS: hoping there is still somebody listening to this list... >   > _______________________________________________ > inet-ops mailing list > inet-ops@puck.nether.net > https://puck.nether.net/mailman/listinfo/inet-ops It's a common spammer tactic for this very reason. I can't give you a good answer though, other than just use one MX and make sure it doesn't fail. From yltnigi@usa.com Wed Oct 22 14:03:40 2003 Received: from someone claiming to be pd9053783.dip.t-dialin.net puck.NOSPAM (pD9053783.dip.t-dialin.net [217.5.55.131]) by puck.nether.net (8.12.10/8.12.9) with SMTP id h9MI3bmQ015844; Wed, 22 Oct 2003 14:03:38 -0400 (envelope-from yltnigi@usa.com) Message-ID: <030u8vx9tdf1c5g8ph063p4i2rw47h@om0rjuch> From: "Laura Rhoades" To: jthomas@puck.nether.net Date: Wed, 22 Oct 2003 10:06:32 -0600 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="8.4E4EABDC_E" Cc: foundry-nsp@puck.nether.net, inet-ops@puck.nether.net Subject: [inet-ops] Beauty Secrets of Hollywood Models! pbacfgefntojb py X-BeenThere: inet-ops@puck.nether.net X-Mailman-Version: 2.1.3 Precedence: list Reply-To: Laura Rhoades List-Id: list for internet operators List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Oct 2003 18:03:41 -0000 --8.4E4EABDC_E Content-Type: text/html; Content-Transfer-Encoding: quoted-printable

As Seen on NBC, CBS,
CNN and even Oprah!


The Health Discovery that Actually Reverses Aging while Burning Fat,
without Dieting or Exercise!

This Proven Discovery has even been reported
on by the New England Journal of Medicine.

Forget Aging and Dieting Forever!

And it's Guaranteed!


Free Shipping within the US!

Click Here to Learn How you can Receive up to 2 Full
Month's Supplies Absolutely FREE!

Would you like to lose weight while you sleep?

No dieting!
No hunger pains!
No Cravings!
No strenuous exercise!

Change Your Life Forever!

1. Body Fat Loss..................82% improvement.
2. Wrinkle Reduction.............61% improvement.
3. Energy Level.....................84% improvement.
4. Muscle Strength................88% improvement.
5. Sexual Potency.................75% improvement.
6. Emotional Stability.............67% improvement.
7. Memory.............................62% improvement.

Get Your FREE 2 Month Supply TODAY!

FREE "Eat Until You're Thin Program"
Lose up to 15 Pounds in 1 to 2 Weeks!

You are receiving this message as a member of the Opt-In
America List. To remove your email address please
click here
We honor all remove requests.

gcam --8.4E4EABDC_E-- From crimson@sidehack.sat.gweep.net Mon Dec 13 13:43:47 2004 Received: from sidehack.sat.gweep.net (sidehack.sat.gweep.net [204.145.148.154]) by puck.nether.net (8.13.1/8.12.9) with SMTP id iBDIhlJq092863 for ; Mon, 13 Dec 2004 13:43:47 -0500 (EST) (envelope-from crimson@sidehack.sat.gweep.net) X-Envelope-From: crimson@sidehack.sat.gweep.net Received: (qmail 1553 invoked by uid 524); 13 Dec 2004 18:43:46 -0000 Date: Mon, 13 Dec 2004 13:43:46 -0500 From: Joe Provo To: inet-ops@puck.nether.net, cidr-reports@potaroo.net Message-ID: <20041213184346.GA99749@gweep.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.1i X-PGP-Key: http://www.gweep.net/~crimson/pgp.txt X-Disclaimer: "I'm the only one foolish enough to claim these opinions." Organization: Russell Street UN*X Consultations: Souls taken in trade for service. X-Do-Not-Email-Here: inhuman@place.rsuc.gweep.net Cc: Michael.Dillon@radianz.com Subject: [inet-ops] Cidr report here? X-BeenThere: inet-ops@puck.nether.net X-Mailman-Version: 2.1.5 Precedence: list Reply-To: jzp-inetops@rsuc.gweep.net List-Id: list for internet operators List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Dec 2004 18:43:48 -0000 Jeared, Geoff, et al, Maybe the cidr report should get distribution here for actual discussion of the data? I got several private replies indicating that the spate of nanog- banning has indeed had a chilling effect on real dialog. I'd like to followup some of Michael's further exmaination of the metrics showing imrpovment, but don't feel it would be intellectually honest to do so in a forum where I know people are interested and have value to add yet are self-censoring. Cc'd to people who publicly commented and may not be on inet-ops, bcc'd to those wwho privately commented for similar reasons. Cheers, Joe -- RSUC / GweepNet / Spunk / FnB / Usenix / SAGE From tom@unitedlayer.com Mon Dec 13 14:15:44 2004 Received: from smtp.unitedlayer.com (smtp.unitedlayer.com [209.237.230.30]) by puck.nether.net (8.13.1/8.12.9) with ESMTP id iBDJFf0q097383 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Mon, 13 Dec 2004 14:15:43 -0500 (EST) (envelope-from tom@unitedlayer.com) X-Envelope-From: tom@unitedlayer.com Received: from localhost (localhost [127.0.0.1]) by smtp.unitedlayer.com (8.13.1/8.11.4) with ESMTP id iBDJFc0F008727; Mon, 13 Dec 2004 11:15:38 -0800 (PST) (envelope-from tom@unitedlayer.com) Date: Mon, 13 Dec 2004 11:15:38 -0800 (PST) From: "Tom (UnitedLayer)" To: inet-ops@puck.nether.net Subject: Re: [inet-ops] Cidr report here? In-Reply-To: <20041213184346.GA99749@gweep.net> Message-ID: <20041213110251.J58714-100000@smtp.unitedlayer.com> X-Accepted-File-Formats: ASCII .rtf .ps - *NO* MS Office files please MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: cidr-reports@potaroo.net X-BeenThere: inet-ops@puck.nether.net X-Mailman-Version: 2.1.5 Precedence: list List-Id: list for internet operators List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Dec 2004 19:15:44 -0000 On Mon, 13 Dec 2004, Joe Provo wrote: > Maybe the cidr report should get distribution here > for actual discussion of the data? I think thats a great idea. > I got several private replies indicating that the spate of nanog- > banning has indeed had a chilling effect on real dialog. I'd say thats right on the money, I know quite a few people who feel exactly the same way - lets go for it! From jared@puck.nether.net Mon Dec 13 23:09:15 2004 Received: from puck.nether.net (puck.nether.net [204.42.254.5]) by puck.nether.net (8.13.1/8.12.9) with ESMTP id iBE49FLb040648 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 13 Dec 2004 23:09:15 -0500 (EST) (envelope-from jared@puck.nether.net) X-Envelope-From: jared@puck.nether.net Received: (from jared@localhost) by puck.nether.net (8.13.1/8.12.9/Submit) id iBE49Fab040647; Mon, 13 Dec 2004 23:09:15 -0500 (EST) (envelope-from jared) Date: Mon, 13 Dec 2004 23:09:15 -0500 From: Jared Mauch To: Joe Provo Subject: Re: [inet-ops] Cidr report here? Message-ID: <20041214040915.GE62919@puck.nether.net> References: <20041213184346.GA99749@gweep.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041213184346.GA99749@gweep.net> User-Agent: Mutt/1.5.6i Cc: Michael.Dillon@radianz.com, cidr-reports@potaroo.net, inet-ops@puck.nether.net X-BeenThere: inet-ops@puck.nether.net X-Mailman-Version: 2.1.5 Precedence: list List-Id: list for internet operators List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Dec 2004 04:09:15 -0000 On Mon, Dec 13, 2004 at 01:43:46PM -0500, Joe Provo wrote: > Jeared, Geoff, et al, Not sure who the Jeared person is, but speaking as a Jared-type of person, i've permitted that address to post to the list. > Maybe the cidr report should get distribution here > for actual discussion of the data? I got several > private replies indicating that the spate of nanog- > banning has indeed had a chilling effect on real > dialog. I'd like to followup some of Michael's > further exmaination of the metrics showing imrpovment, > but don't feel it would be intellectually honest > to do so in a forum where I know people are interested > and have value to add yet are self-censoring. > > Cc'd to people who publicly commented and may not > be on inet-ops, bcc'd to those wwho privately > commented for similar reasons. sure, i'm fairly straighforward with the lists that i host, i want them to be of techincal value and not sales stuff. i could also create a cidr-report-discuss type list, but a forum like this would probally be better suited, as it may get a broader audience. (but i could also be wrong). - jared -- Jared Mauch | pgp key available via finger from jared@puck.nether.net clue++; | http://puck.nether.net/~jared/ My statements are only mine. From randy@psg.com Mon Dec 13 23:23:36 2004 Received: from ran.psg.com (ip192.186.dsl-acs2.seawa0.iinet.com [209.20.186.192]) by puck.nether.net (8.13.1/8.12.9) with ESMTP id iBE4NZT8041833 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Mon, 13 Dec 2004 23:23:36 -0500 (EST) (envelope-from randy@psg.com) X-Envelope-From: randy@psg.com Received: from localhost ([127.0.0.1] helo=ran.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.43 (FreeBSD)) id 1Ce4Dm-000Eps-Pc for inet-ops@puck.nether.net; Mon, 13 Dec 2004 20:23:34 -0800 From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16830.27334.385092.878719@ran.psg.com> Date: Mon, 13 Dec 2004 20:23:34 -0800 To: inet-ops@puck.nether.net Subject: Re: [inet-ops] Cidr report here? References: <20041213184346.GA99749@gweep.net> <20041214040915.GE62919@puck.nether.net> X-BeenThere: inet-ops@puck.nether.net X-Mailman-Version: 2.1.5 Precedence: list List-Id: list for internet operators List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Dec 2004 04:23:36 -0000 as folk are censored by an fool from another non-ops-run list, having this as one place to discuss the cidr and ris reports would be good. the real question is what can effectively be done to get clueless crap out of the routing tables. the s/n in bgp approaches that of a mailing list. but it may easier to apply technology to the bgp universe; e.g., see discussion on c-nsp of auto-drop of covered prefixes. to get actual discussion moving, my opinion is appended. randy --- From: randy at psg.com (Randy Bush) Date: Wed Dec 1 20:51:25 2004 Subject: [c-nsp] Growing BGP tables References: <0D6AB216-4403-11D9-8994-000D93282A96@Hughes.com.au> Message-ID: <16814.29973.27522.38883@ran.psg.com> i proposed to rodney today, there are three types of prefix pollution. o pure crap, such as that we see on top of the weekly report o someone traffic engineering o legitimate holes (someone moving from at&t's 12/8) a hardcore such as i might just filter them all a friendlier type might just dump longer prefixes if they had the same origin asn (the new part of the suggestion) a southern californian might only dump a longer prefix if it has the same next hop as the covering prefix randy From crimson@sidehack.sat.gweep.net Tue Dec 14 03:16:15 2004 Received: from sidehack.sat.gweep.net (sidehack.sat.gweep.net [204.145.148.154]) by puck.nether.net (8.13.1/8.12.9) with SMTP id iBE8GEEG066050 for ; Tue, 14 Dec 2004 03:16:15 -0500 (EST) (envelope-from crimson@sidehack.sat.gweep.net) X-Envelope-From: crimson@sidehack.sat.gweep.net Received: (qmail 38900 invoked by uid 524); 14 Dec 2004 08:16:14 -0000 Date: Tue, 14 Dec 2004 03:16:14 -0500 From: Joe Provo To: Jared Mauch Subject: Re: [inet-ops] Cidr report here? Message-ID: <20041214081612.GA38191@gweep.net> References: <20041213184346.GA99749@gweep.net> <20041214040915.GE62919@puck.nether.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041214040915.GE62919@puck.nether.net> User-Agent: Mutt/1.4.2.1i X-PGP-Key: http://www.gweep.net/~crimson/pgp.txt X-Disclaimer: "I'm the only one foolish enough to claim these opinions." Organization: RSUC - We accept paypal payments. See https://www.paypal.com/refer/pal=BDQAC5VVRP68U X-Do-Not-Email-Here: quiet@place.rsuc.gweep.net Cc: inet-ops@puck.nether.net X-BeenThere: inet-ops@puck.nether.net X-Mailman-Version: 2.1.5 Precedence: list Reply-To: jzp-inetops@rsuc.gweep.net List-Id: list for internet operators List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Dec 2004 08:16:17 -0000 On Mon, Dec 13, 2004 at 11:09:15PM -0500, Jared Mauch wrote: > On Mon, Dec 13, 2004 at 01:43:46PM -0500, Joe Provo wrote: > > Jeared, Geoff, et al, > > Not sure who the Jeared person is, but speaking as > a Jared-type of person, i've permitted that address to post to the > list. As well as "Jared, master of Puck" you'll also going to be known as "Jared, forgiver of typos". :-P > i could also create a cidr-report-discuss type list, but a forum > like this would probally be better suited, as it may get a broader > audience. (but i could also be wrong). My point exactly; rather than pigeonhole into something specifically about the report, it is high time this available generalized discussion forum was used. Hopefully it will spur additional use of this resource. As ever, thanks! Joe -- RSUC / GweepNet / Spunk / FnB / Usenix / SAGE From Michael.Dillon@radianz.com Tue Dec 14 05:57:32 2004 Received: from intldssmtp001.radianz.com (intldssmtp001.radianz.com [195.16.185.40]) by puck.nether.net (8.13.1/8.12.9) with ESMTP id iBEAvVEo084088 for ; Tue, 14 Dec 2004 05:57:32 -0500 (EST) (envelope-from Michael.Dillon@radianz.com) X-Envelope-From: Michael.Dillon@radianz.com To: inet-ops@puck.nether.net MIME-Version: 1.0 X-Mailer: Lotus Notes Release 6.5 September 26, 2003 Message-ID: From: Michael.Dillon@radianz.com Date: Tue, 14 Dec 2004 10:58:14 +0000 X-MIMETrack: Serialize by Router on INTLDSSMTP001/SERV/RadianzExt(Release 6.5.2|June 01, 2004) at 14/12/2004 11:06:13, Serialize complete at 14/12/2004 11:06:13 Content-Type: text/plain; charset="US-ASCII" Subject: [inet-ops] Prefix Pollution X-BeenThere: inet-ops@puck.nether.net X-Mailman-Version: 2.1.5 Precedence: list List-Id: list for internet operators List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Dec 2004 10:57:32 -0000 I generally agree with Randy's viewpoint on this. However, I think that the problem of pollution arises from people's behavior and there are some social engineering actions that can help. For instance back in 2001 there was a lot of publicity about the problem but then around the time that Cengiz presented his findings, it seemed like the telecom collapse had solved the problem. I think a lot of people who could be cleaning up their announcements have put this mentally on the back burner. >i proposed to rodney today, there are three types of prefix >pollution. > o pure crap, such as that we see on top of the weekly > report > o someone traffic engineering > o legitimate holes (someone moving from at&t's 12/8) I like this. If we can come up with some reasonable definitions for this then perhaps we can talk Team Cymru into providing these "prefix attributes" as yet another feed. The bogon feed has a growing profile and the fact that RIRs regularly release new /8's helps keep this issue alive. I wouldn't want this to be just jumbled with the bogon feed, but a separate feed of "prefix pollution" would be just about right. The big task is going to be identifying the traffic engineering and the legitimate holes. That's where this list could be helpful so that people can explain what they are really doing with their shorter prefixes in case they get misclassified. --Michael Dillon From crimson@sidehack.sat.gweep.net Tue Dec 14 06:27:04 2004 Received: from sidehack.sat.gweep.net (sidehack.sat.gweep.net [204.145.148.154]) by puck.nether.net (8.13.1/8.12.9) with SMTP id iBEBR3DN088042 for ; Tue, 14 Dec 2004 06:27:03 -0500 (EST) (envelope-from crimson@sidehack.sat.gweep.net) X-Envelope-From: crimson@sidehack.sat.gweep.net Received: (qmail 12646 invoked by uid 524); 14 Dec 2004 11:27:03 -0000 Date: Tue, 14 Dec 2004 06:27:03 -0500 From: Joe Provo To: inet-ops@puck.nether.net Subject: Re: [inet-ops] Prefix Pollution Message-ID: <20041214112703.GA10178@gweep.net> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i X-PGP-Key: http://www.gweep.net/~crimson/pgp.txt X-Disclaimer: "I'm the only one foolish enough to claim these opinions." Organization: RSUC: Souls taken in trade for service. X-Do-Not-Email-Here: fragrant@place.rsuc.gweep.net X-BeenThere: inet-ops@puck.nether.net X-Mailman-Version: 2.1.5 Precedence: list Reply-To: jzp-inetops@rsuc.gweep.net List-Id: list for internet operators List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Dec 2004 11:27:04 -0000 On Tue, Dec 14, 2004 at 10:58:14AM +0000, Michael.Dillon@radianz.com wrote: [snip] > The big task is going to be identifying the > traffic engineering and the legitimate holes. > That's where this list could be helpful so that > people can explain what they are really doing > with their shorter prefixes in case they get > misclassified. I many be a bit stodgey in this regard, but what comprises 'legitimate traffic engineering' that needs to be seen in the DFZ? It is trivial to leak deaggregates to one's providers tagged NO_EXPORT. Beyond the radius of $s flowing, what is 'legitimate'? And 'company already doing it at a flag day' or 'company who employs $person' aren't acceptable answers. The litmus test of 'breaks reachability' isn't much of a bar, as people are going out of their way to do that with no discernable benefit. Likely some combination of 'breaks reachability' and 'not trivially reduced by as-path' needs to be concocted, as there are many many trivial examples that from N arbitrary ASNs away have no differentiation in path. I'm not even talking about 'global corporation carving their legacy allocations up' or 'global entity behind nat/firewall exposing small slices as DMZes'... off the top of my head, Nestle US: route-views.oregon-ix.net>sho ip bgp 165.131.0.0/16 lo | inc / * 165.131.118.0/23 196.7.106.245 0 0 2905 701 7018 31880 ? * 165.131.124.0/23 196.7.106.245 0 0 2905 701 7018 31880 ? * 165.131.174.0/23 196.7.106.245 0 0 2905 701 7018 31880 ? route-views.oregon-ix.net>sho ip bgp quote-reg "_31880" | inc / * 165.131.118.0/23 196.7.106.245 0 0 2905 701 7018 31880 ? * 165.131.124.0/23 196.7.106.245 0 0 2905 701 7018 31880 ? * 165.131.174.0/23 196.7.106.245 0 0 2905 701 7018 31880 ? route-views.oregon-ix.net>sho ip bgp quote-reg "_31880" | ex 7018 BGP table version is 23826096, local router ID is 198.32.162.100 Status codes: s suppressed, d damped, h history, * valid, > best, i - internal, S Stale Origin codes: i - IGP, e - EGP, ? - incomplete Network Next Hop Metric LocPrf Weight Path route-views.oregon-ix.net> joe -- RSUC / GweepNet / Spunk / FnB / Usenix / SAGE From ralph@istop.com Tue Dec 14 07:47:02 2004 Received: from smtp.istop.com (smtp.istop.com [66.11.167.126]) by puck.nether.net (8.13.1/8.12.9) with ESMTP id iBECl1HE095611 for ; Tue, 14 Dec 2004 07:47:02 -0500 (EST) (envelope-from ralph@istop.com) X-Envelope-From: ralph@istop.com Received: from ns.istop.com (ns.istop.com [66.11.168.199]) by smtp.istop.com (Postfix) with ESMTP id D73E72B4B1 for ; Tue, 14 Dec 2004 07:48:20 -0500 (EST) Date: Tue, 14 Dec 2004 07:46:57 -0500 (EST) From: Ralph Doncaster To: "inet-ops@puck.nether.net" Subject: Re: [inet-ops] Prefix Pollution In-Reply-To: Message-ID: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-BeenThere: inet-ops@puck.nether.net X-Mailman-Version: 2.1.5 Precedence: list Reply-To: ralph+d@istop.com List-Id: list for internet operators List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Dec 2004 12:47:02 -0000 On Tue, 14 Dec 2004, Michael.Dillon@radianz.com wrote: > However, I think that the problem of pollution arises > from people's behavior and there are some social > engineering actions that can help. Many customers are not aware of Arin's /22 policy, and for those that are aware, there's often no incentive to apply for their own block. For example I had a customer that was reassigned a /23 and /24 from my /19. They were multi-homed, and were also reassigned IPs from another transit provider. We charge a modest amount for reassignments ($35/mth per /24) but the other provider (like most) doesn't. After the /22 policy came out I told the customer they should get their own /22. They didn't. Eventually I told them I was taking back the IPs and gave them 2 months to renumber. The whole process took so much work I can see why most networks would rather just do nothing. Updating RR objects isn't too bad since it is automated, but upstream filter updates generally are not. In many cases it takes more than just an email to an upstream to get filter changes done. I susupect the big networks don't even know which customers would qualify for direct assignment, so nothing will happen in this case. One simple thing I think that would help is if transit providers set their filters to allow for aggregation. Let's say I'm announcing 67.8.64.0/22. My upstreams will add this to their filters ... permit 67.8.64.0/22 Why not add this instead? ... permit 67.8.64.0/18 le 22 Overall though, I think it's a rather steep uphill battle... -Ralph From ralph@istop.com Tue Dec 14 07:59:00 2004 Received: from smtp.istop.com (smtp.istop.com [66.11.167.126]) by puck.nether.net (8.13.1/8.12.9) with ESMTP id iBECwwbc096542 for ; Tue, 14 Dec 2004 07:59:00 -0500 (EST) (envelope-from ralph@istop.com) X-Envelope-From: ralph@istop.com Received: from ns.istop.com (ns.istop.com [66.11.168.199]) by smtp.istop.com (Postfix) with ESMTP id 343082B4D9 for ; Tue, 14 Dec 2004 08:00:21 -0500 (EST) Date: Tue, 14 Dec 2004 07:58:58 -0500 (EST) From: Ralph Doncaster To: "inet-ops@puck.nether.net" Subject: Re: [inet-ops] Cidr report here? In-Reply-To: <16830.27334.385092.878719@ran.psg.com> Message-ID: References: <20041213184346.GA99749@gweep.net> <20041214040915.GE62919@puck.nether.net> <16830.27334.385092.878719@ran.psg.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-BeenThere: inet-ops@puck.nether.net X-Mailman-Version: 2.1.5 Precedence: list Reply-To: ralph+d@istop.com List-Id: list for internet operators List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Dec 2004 12:59:00 -0000 On Mon, 13 Dec 2004, Randy Bush wrote: > the real question is what can effectively be done to get > clueless crap out of the routing tables. The design of BGP favors the crap, so you'll have to redesign BGP. ;-) I don't want to aggregate the routes I send to my customers because: a) I'll get less of their traffic b) the customers will ask why they're not getting a full table -Ralph From randy@psg.com Tue Dec 14 09:45:59 2004 Received: from ran.psg.com (ip192.186.dsl-acs2.seawa0.iinet.com [209.20.186.192]) by puck.nether.net (8.13.1/8.12.9) with ESMTP id iBEEjwXb013709 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Tue, 14 Dec 2004 09:45:59 -0500 (EST) (envelope-from randy@psg.com) X-Envelope-From: randy@psg.com Received: from localhost ([127.0.0.1] helo=ran.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.43 (FreeBSD)) id 1CeDw5-0007L6-QL; Tue, 14 Dec 2004 06:45:57 -0800 From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16830.64677.306250.535768@ran.psg.com> Date: Tue, 14 Dec 2004 06:45:57 -0800 To: Michael.Dillon@radianz.com Subject: Re: [inet-ops] Prefix Pollution References: Cc: inet-ops@puck.nether.net X-BeenThere: inet-ops@puck.nether.net X-Mailman-Version: 2.1.5 Precedence: list List-Id: list for internet operators List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Dec 2004 14:46:00 -0000 >> i proposed to rodney today, there are three types of prefix >> pollution. >> o pure crap, such as that we see on top of the weekly >> report >> o someone traffic engineering >> o legitimate holes (someone moving from at&t's 12/8) > > I like this. If we can come up with some reasonable > definitions for this then perhaps we can talk > Team Cymru into providing these "prefix attributes" absolutely no need. engage brain, please. > The big task is going to be identifying the > traffic engineering and the legitimate holes. they are self-identifying. shift brain to second gear. or just read the rest of my message. a hardcore such as i might just filter them all a friendlier type might just dump longer prefixes if they had the same origin asn (the new part of the suggestion) a southern californian might only dump a longer prefix if it has the same next hop as the covering prefix randy From crimson@sidehack.sat.gweep.net Tue Dec 14 10:14:11 2004 Received: from sidehack.sat.gweep.net (sidehack.sat.gweep.net [204.145.148.154]) by puck.nether.net (8.13.1/8.12.9) with SMTP id iBEFEA0v016544 for ; Tue, 14 Dec 2004 10:14:10 -0500 (EST) (envelope-from crimson@sidehack.sat.gweep.net) X-Envelope-From: crimson@sidehack.sat.gweep.net Received: (qmail 53557 invoked by uid 524); 14 Dec 2004 15:14:10 -0000 Date: Tue, 14 Dec 2004 10:14:10 -0500 From: Joe Provo To: inet-ops@puck.nether.net Subject: Re: [inet-ops] Prefix Pollution Message-ID: <20041214151410.GA50393@gweep.net> References: <16830.64677.306250.535768@ran.psg.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <16830.64677.306250.535768@ran.psg.com> User-Agent: Mutt/1.4.2.1i X-PGP-Key: http://www.gweep.net/~crimson/pgp.txt X-Disclaimer: "I'm the only one foolish enough to claim these opinions." Organization: RSUC: Souls taken in trade for service. X-Do-Not-Email-Here: no@place.rsuc.gweep.net X-BeenThere: inet-ops@puck.nether.net X-Mailman-Version: 2.1.5 Precedence: list Reply-To: jzp-inetops@rsuc.gweep.net List-Id: list for internet operators List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Dec 2004 15:14:11 -0000 On Tue, Dec 14, 2004 at 06:45:57AM -0800, Randy Bush wrote: [snip] > a hardcore such as i might just filter them all > > a friendlier type might just dump longer prefixes if they > had the same origin asn (the new part of the suggestion) > > a southern californian might only dump a longer prefix > if it has the same next hop as the covering prefix Part of 'what action should i take' also falls under 'what is least effort'. MD pointed on that other list to the CAIDA Atoms work [http://www.caida.org/projects/routing/atoms/] which is very cool, but requires one of - non-realtime offline processing [boo] - vendors to incorporate their own proprietary and buggy code to do the same thing [in a glacial epoch] - people to junk vendors and solder their own interface boards in the garage [didn't we do that before?] ...so many times the analysis comes back to "accept everything and only react to outside-influence-of-the-moment" or "follow allocation guidelines for a baseline filter and adjust as business needs dictate". Does either approach nescessarily lead to better stability and goodput? I have my opinions based on my experiences, but am not so full of hubris to think mine is the only point of view that counts. A HUGE portion of my poking-the-stick into this nest isa to see if there are hornets in it ["yes this is still 'an issue' and somehow we were collectively asleep at the wheel of the DFZ"] or not ["no, the general consensus is that if you haven't upgraded in the last X years, and can't budget for unpredicatble growth, then get out of the game"]. Joe, setting religion on the shelf for a bit to get data -- RSUC / GweepNet / Spunk / FnB / Usenix / SAGE From randy@psg.com Tue Dec 14 10:32:14 2004 Received: from ran.psg.com (ip192.186.dsl-acs2.seawa0.iinet.com [209.20.186.192]) by puck.nether.net (8.13.1/8.12.9) with ESMTP id iBEFWDj6019886 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Tue, 14 Dec 2004 10:32:14 -0500 (EST) (envelope-from randy@psg.com) X-Envelope-From: randy@psg.com Received: from localhost ([127.0.0.1] helo=ran.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.43 (FreeBSD)) id 1CeEep-0008qH-TG; Tue, 14 Dec 2004 07:32:12 -0800 From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16831.1915.396109.805489@ran.psg.com> Date: Tue, 14 Dec 2004 07:32:11 -0800 To: Joe Provo Subject: Re: [inet-ops] Prefix Pollution References: <16830.64677.306250.535768@ran.psg.com> <20041214151410.GA50393@gweep.net> Cc: inet-ops@puck.nether.net X-BeenThere: inet-ops@puck.nether.net X-Mailman-Version: 2.1.5 Precedence: list List-Id: list for internet operators List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Dec 2004 15:32:14 -0000 > Part of 'what action should i take' also falls under 'what > is least effort'. MD pointed on that other list to the > CAIDA Atoms work [http://www.caida.org/projects/routing/atoms/] > which is very cool, but requires one of > ... which is why it is, sadly, kinda operationally irrelevant. bummer that. > ...so many times the analysis comes back to "accept everything > and only react to outside-influence-of-the-moment" or "follow > allocation guidelines for a baseline filter and adjust as > business needs dictate". you don't think what was discussed on c-nsp is o simple enough code the vendors might get it right on the third try, and o has the knobs you need to set reasonable (to you) policy? if not, why not? randy From randy@psg.com Tue Dec 14 12:12:33 2004 Received: from ran.psg.com (ip192.186.dsl-acs2.seawa0.iinet.com [209.20.186.192]) by puck.nether.net (8.13.1/8.12.9) with ESMTP id iBEHCVP8032475 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Tue, 14 Dec 2004 12:12:32 -0500 (EST) (envelope-from randy@psg.com) X-Envelope-From: randy@psg.com Received: from localhost ([127.0.0.1] helo=ran.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.43 (FreeBSD)) id 1CeGDv-000Bui-Ck for inet-ops@puck.nether.net; Tue, 14 Dec 2004 09:12:31 -0800 From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16831.7934.986112.63889@ran.psg.com> Date: Tue, 14 Dec 2004 09:12:30 -0800 To: inet-ops@puck.nether.net Subject: [inet-ops] DC Qwestion X-BeenThere: inet-ops@puck.nether.net X-Mailman-Version: 2.1.5 Precedence: list List-Id: list for internet operators List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Dec 2004 17:12:33 -0000 smb asks via cell if qwest is having problems in the dc area? randy From randy@psg.com Tue Dec 14 13:32:33 2004 Received: from ran.psg.com (ip192.186.dsl-acs2.seawa0.iinet.com [209.20.186.192]) by puck.nether.net (8.13.1/8.12.9) with ESMTP id iBEIWWWu043685 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Tue, 14 Dec 2004 13:32:33 -0500 (EST) (envelope-from randy@psg.com) X-Envelope-From: randy@psg.com Received: from localhost ([127.0.0.1] helo=ran.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.43 (FreeBSD)) id 1CeHTK-000EFS-QZ; Tue, 14 Dec 2004 10:32:30 -0800 From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16831.12734.312276.628044@ran.psg.com> Date: Tue, 14 Dec 2004 10:32:30 -0800 To: "Hannigan, Martin" Subject: Re: [inet-ops] DC Qwestion References: Cc: inet-ops@puck.nether.net X-BeenThere: inet-ops@puck.nether.net X-Mailman-Version: 2.1.5 Precedence: list List-Id: list for internet operators List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Dec 2004 18:32:33 -0000 > I'm in boston this week and have been yapping on cells all day in the dc > area. >> smb asks via cell if qwest is having problems in the dc area? sorry. i meant smb had used his mobile to ask if qwest was known to be having internet problems in dc area. he is in meetings and can't net out. randy From crimson@sidehack.sat.gweep.net Wed Dec 15 22:28:49 2004 Received: from sidehack.sat.gweep.net (sidehack.sat.gweep.net [204.145.148.154]) by puck.nether.net (8.13.1/8.12.9) with SMTP id iBG3SmkU058795 for ; Wed, 15 Dec 2004 22:28:48 -0500 (EST) (envelope-from crimson@sidehack.sat.gweep.net) X-Envelope-From: crimson@sidehack.sat.gweep.net Received: (qmail 64947 invoked by uid 524); 16 Dec 2004 03:28:48 -0000 Date: Wed, 15 Dec 2004 22:28:48 -0500 From: Joe Provo To: inet-ops@puck.nether.net Subject: Re: [inet-ops] Prefix Pollution Message-ID: <20041216032847.GA62506@gweep.net> References: <16830.64677.306250.535768@ran.psg.com> <20041214151410.GA50393@gweep.net> <16831.1915.396109.805489@ran.psg.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <16831.1915.396109.805489@ran.psg.com> User-Agent: Mutt/1.4.2.1i X-PGP-Key: http://www.gweep.net/~crimson/pgp.txt X-Disclaimer: "I'm the only one foolish enough to claim these opinions." Organization: RSUC - If we don't do it, you don't need it. X-Do-Not-Email-Here: offal@place.rsuc.gweep.net X-BeenThere: inet-ops@puck.nether.net X-Mailman-Version: 2.1.5 Precedence: list Reply-To: jzp-inetops@rsuc.gweep.net List-Id: list for internet operators List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Dec 2004 03:28:49 -0000 On Tue, Dec 14, 2004 at 07:32:11AM -0800, Randy Bush wrote: [snip] > > ...so many times the analysis comes back to "accept everything > > and only react to outside-influence-of-the-moment" or "follow > > allocation guidelines for a baseline filter and adjust as > > business needs dictate". > > you don't think what was discussed on c-nsp is > o simple enough code the vendors might get it right on > the third try, and > o has the knobs you need to set reasonable (to you) > policy? > > if not, why not? I'm under the weather so need to re-read both the pseudo-code that was bounced around and draft-hardie-bounded-longest-match to give an informed reponses. I am compelled to not let the attempt to have real discussion here fall down just because of my lack of input. My gut feeling is that for some deployments where this is a concern [multihoming smaller enterprises], restricting to next-hop would not be appropriate and that a knob for next-hop or neighbor-AS would be needed. Given the nature of current vendor-implementations of ebgp policy knobs and the way folks have cleverly deployed them, I would think not closing too many doors would be in the best interest of all. So yes I'd suggest giving operators enough rope to hang themselves if they go overboard, by providing supressing remote more-specifics ['bounding the longest match'] on a number of policy axes: next-hop [straightforward seen as the Right Thing] router-id [not nescessarily the same as above - also consider the wildly useful variation of router-id to trigger the neighbor's supression anologous to the clever use of RPF to trigger blackholes today] neighbor AS [to address local next-hop related complexities] MED ("i wish to get the more-specifics if my neighbor tells me there is value") Origin (similar to above point) It essentially comes down to how much 'sameness' is needed to consider them identical? If we don't cover for minor variances lower down the decisions tree then suddenly those 'lower points' become very significant knobs to turn. I can see people arguing with me about that [MED and origin]; I can table that for now. Router ID seems natural and trivial if we're already inspecting next-hop. I will strenuously argue that neighbor ASN be considered, specifically to speak to Mr Donacaster's point. This provides the simple multihoming the end-customers automatic control over attemtps to siphon their traffic; consquently there is no economic incentive for those customers' providers to tacitly encourage table pollution. In the simplified case of - two multihomed enterprises, one of which (a) announces extra crap and the other (b) who doesn't want to hear it and - two transit carriers, one of which (c) deploys the new feature and the other which (d) does not +-- C --+ / \ A --- D --- B C presents A's long prefix to B D presents A's long and short prefixes to B B has paralel links ro D, attached to the same border within B and disparate aggregation devices in D. supression based on next-hop or even router-id couldn't comparison wouldn't help poor B. based on AS would. Neighbor-AS-based comparison also simplifies configuration [ports and therefore next-hop migrate more frequently than ASNs do], and we are told time and again that root causes of most network issues are configuration-wrangling related. In the long term, we [or our memetic descendants] are likely to be discussing the centralized nature of this point on the decision tree and a RIB-vs-FIB issue just as we all went round the separating-a-distributed-FIB-from-centralized-RIB maypole in the mid->latter 90s. Cheers, joe -- RSUC / GweepNet / Spunk / FnB / Usenix / SAGE From crimson@sidehack.sat.gweep.net Wed Dec 15 23:50:51 2004 Received: from sidehack.sat.gweep.net (sidehack.sat.gweep.net [204.145.148.154]) by puck.nether.net (8.13.1/8.12.9) with SMTP id iBG4op5l064349 for ; Wed, 15 Dec 2004 23:50:51 -0500 (EST) (envelope-from crimson@sidehack.sat.gweep.net) X-Envelope-From: crimson@sidehack.sat.gweep.net Received: (qmail 78009 invoked by uid 524); 16 Dec 2004 04:50:50 -0000 Date: Wed, 15 Dec 2004 23:50:50 -0500 From: Joe Provo To: inet-ops@puck.nether.net Message-ID: <20041216045050.GA74495@gweep.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.1i X-PGP-Key: http://www.gweep.net/~crimson/pgp.txt X-Disclaimer: "I'm the only one foolish enough to claim these opinions." Organization: Russell Street UN*X Consultations: Fighting the Conspiracy since 1985 X-Do-Not-Email-Here: sticky@spammers.can-bite-me.com Subject: [inet-ops] Anycast stability experiment results? X-BeenThere: inet-ops@puck.nether.net X-Mailman-Version: 2.1.5 Precedence: list Reply-To: jzp-inetops@rsuc.gweep.net List-Id: list for internet operators List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Dec 2004 04:50:52 -0000 By the way, has there been any initial data from the near-month of data being collected by users of http://rip.psg.com/~randy/anycast_gatherer-1.4.tar.gz ...or where should we watch for more details, since presumably one if not more locations of its announcement is not likely to be re-visited by the authors? randy had said: > [ fyi, my personal bet is that it's usually pretty stable except > for sites in strangely unstable routing environments. but i am > under my quota of wrong for the week. ] My opinion extends to presuming that networks with issues visible in off-net anycast are generally not deterministic in steady state and fail the third need of goodput in the classic "paths must be short, fast and stable" troika. Cheers, Joe -- RSUC / GweepNet / Spunk / FnB / Usenix / SAGE From randy@psg.com Thu Dec 16 00:36:45 2004 Received: from ran.psg.com (ip192.186.dsl-acs2.seawa0.iinet.com [209.20.186.192]) by puck.nether.net (8.13.1/8.12.9) with ESMTP id iBG5aiLo069388 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Thu, 16 Dec 2004 00:36:45 -0500 (EST) (envelope-from randy@psg.com) X-Envelope-From: randy@psg.com Received: from localhost ([127.0.0.1] helo=ran.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.43 (FreeBSD)) id 1CeoJe-000MRD-TA; Wed, 15 Dec 2004 21:36:43 -0800 From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16833.7914.394266.619269@ran.psg.com> Date: Wed, 15 Dec 2004 21:36:42 -0800 To: Joe Provo Subject: Re: [inet-ops] Anycast stability experiment results? References: <20041216045050.GA74495@gweep.net> Cc: inet-ops@puck.nether.net X-BeenThere: inet-ops@puck.nether.net X-Mailman-Version: 2.1.5 Precedence: list List-Id: list for internet operators List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Dec 2004 05:36:45 -0000 > By the way, has there been any initial data from the near-month of > data being collected by users of > http://rip.psg.com/~randy/anycast_gatherer-1.4.tar.gz > ...or where should we watch for more details, since presumably one > if not more locations of its announcement is not likely to be > re-visited by the authors? i believe, but could be very wrong, that the measurement has been stopped on all hosts except some planetlab nodes (we want to be able to compare planetlab to the real internet). peter is a grad student, and finals were last week. so he is just starting to take the first looks at the data. for starters, he says he is trying to look at geo and topo distribution of both sources and responding servers. randy From randy@psg.com Wed Jan 5 02:18:02 2005 Received: from rip.psg.com (rip.psg.com [147.28.0.39]) by puck.nether.net (8.13.2/8.12.9) with ESMTP id j057I1k6058560 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Wed, 5 Jan 2005 02:18:02 -0500 (EST) (envelope-from randy@psg.com) X-Envelope-From: randy@psg.com Received: from localhost ([127.0.0.1] helo=roam.psg.com) by rip.psg.com with esmtp (Exim 4.43 (FreeBSD)) id 1Cm5Qf-0004kX-Db for inet-ops@puck.nether.net; Wed, 05 Jan 2005 07:18:01 +0000 Received: from localhost ([127.0.0.1] helo=roam.psg.com.psg.com) by roam.psg.com with esmtp (Exim 4.43 (FreeBSD)) id 1Cm5Qc-0002ZI-IH for inet-ops@puck.nether.net; Tue, 04 Jan 2005 21:17:58 -1000 From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16859.38053.717987.595959@roam.psg.com> Date: Tue, 4 Jan 2005 21:17:57 -1000 To: inet-ops@puck.nether.net Subject: [inet-ops] redist with unknown but opt path attr X-BeenThere: inet-ops@puck.nether.net X-Mailman-Version: 2.1.5 Precedence: list List-Id: list for internet operators List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Jan 2005 07:18:02 -0000 if you receive a route with an optional transitive path attribute that you do not understand, do all significant vendors follow route redistribution rules when deciding whether to pass the route on to your bgp (well, e-bgp) neighbors? randy From randy@psg.com Wed Mar 9 15:02:43 2005 Received: from rip.psg.com (rip.psg.com [147.28.0.39]) by puck.nether.net (8.13.3/8.12.9) with ESMTP id j29K2hZM089676 for ; Wed, 9 Mar 2005 15:02:43 -0500 (EST) (envelope-from randy@psg.com) X-Envelope-From: randy@psg.com Received: from localhost ([127.0.0.1] helo=roam.psg.com) by rip.psg.com with esmtp (Exim 4.44 (FreeBSD)) id 1D97OD-000OVq-W2; Wed, 09 Mar 2005 20:02:42 +0000 Received: from localhost ([127.0.0.1] helo=roam.psg.com.psg.com) by roam.psg.com with esmtp (Exim 4.44 (FreeBSD)) id 1D97OB-0005PL-7R; Wed, 09 Mar 2005 10:02:39 -1000 From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16943.22110.100859.97051@roam.psg.com> Date: Wed, 9 Mar 2005 10:02:38 -1000 To: John Payne Subject: Re: [inet-ops] Anycast stability experiment results? References: <20041216045050.GA74495@gweep.net> <16833.7914.394266.619269@ran.psg.com> <8dc5236e0dc3d9b9040f58b9ae907d93@sackheads.org> Cc: inet-ops@puck.nether.net X-BeenThere: inet-ops@puck.nether.net X-Mailman-Version: 2.1.6b1 Precedence: list List-Id: list for internet operators List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Mar 2005 20:02:43 -0000 > Any news on this? *extremely* initial results, which have now known but minor errors, were presented at apnic. see better analysis will be available in a week. imiho, the bottom line is that anycast amplifies effects of bgp/igp twitchiness. randy From leo@ripe.net Wed Apr 20 15:06:26 2005 Received: from postman.ripe.net (postman.ripe.net [193.0.0.199]) by puck.nether.net (8.13.3/8.12.9) with ESMTP id j3KJ6QEf060173 for ; Wed, 20 Apr 2005 15:06:26 -0400 (EDT) (envelope-from leo@ripe.net) X-Envelope-From: leo@ripe.net Received: by postman.ripe.net (Postfix, from userid 8) id 1ABDB25B1D; Wed, 20 Apr 2005 21:06:25 +0200 (CEST) Received: from birch.ripe.net (birch.ripe.net [193.0.1.96]) by postman.ripe.net (Postfix) with ESMTP id 3FED625B00; Wed, 20 Apr 2005 21:06:24 +0200 (CEST) Received: from [IPv6:::1] (cow.ripe.net [193.0.1.239]) by birch.ripe.net (8.12.10/8.11.6) with ESMTP id j3KJ6Met025808; Wed, 20 Apr 2005 21:06:22 +0200 Mime-Version: 1.0 (Apple Message framework v622) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <4144ae2fc48b47f31c274f2605a868d1@ripe.net> Content-Transfer-Encoding: 7bit From: leo vegoda Date: Wed, 20 Apr 2005 15:06:26 -0400 To: afnog@afnog.org, eof-list@ripe.net, sanog@sanog.org, , inet-ops@puck.nether.net, nznog@list.waikato.ac.nz X-Mailer: Apple Mail (2.622) X-RIPE-Spam-Level: X-RIPE-Spam-Tests: ALL_TRUSTED,BAYES_00 X-RIPE-Spam-Status: N 0.020711 / -5.9 X-RIPE-Signature: 30a6790f5e07d0e97a3beb54ba0f6eac Subject: [inet-ops] RIPE NCC to begin allocating from 87/8 X-BeenThere: inet-ops@puck.nether.net X-Mailman-Version: 2.1.6b1 Precedence: list List-Id: list for internet operators List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Apr 2005 19:06:27 -0000 Dear Colleagues, This announcement is being sent to multiple lists. I apologise for duplicates. The RIPE NCC received the IPv4 address range 85.0.0.0 - 88.255.255.255 (85/8, 86/7 and 88/8) from the IANA in April 2004. We began making allocation from 85/8 in August 2004 and from 86/8 in March, this year. We expect to start making allocations from 87/8 in the next few weeks. We have been announcing two prefixes from 87/8: 87.192.0.0/16 and 87.255.248.0/21, which originated in AS12654. These announcements have now been withdrawn as we will start to allocate from this /8. We are currently announcing two prefixes from 88/8, from which we will allocate in a few months. Those announcements are: 88.192.0.0/16 and 88.255.248.0/21, originating in AS12654. Details of the BGP announcements, reachability tools and other information are available on our web site at: http://www.ris.ripe.net/debogon/debogon.html You may want to update any filters you have in place. Kind regards, -- leo vegoda Registration Services Manager RIPE NCC From crimson@sidehack.sat.gweep.net Sun May 1 09:08:05 2005 Received: from sidehack.sat.gweep.net (sidehack.sat.gweep.net [204.145.148.154]) by puck.nether.net (8.13.3/8.12.9) with SMTP id j41D84NG052515 for ; Sun, 1 May 2005 09:08:05 -0400 (EDT) (envelope-from crimson@sidehack.sat.gweep.net) X-Envelope-From: crimson@sidehack.sat.gweep.net Received: (qmail 20280 invoked by uid 524); 1 May 2005 13:08:04 -0000 Date: Sun, 1 May 2005 09:08:04 -0400 From: Joe Provo To: inet-ops@puck.nether.net Subject: Re: [inet-ops] Anycast stability experiment results? Message-ID: <20050501130804.GA20062@gweep.net> References: <20041216045050.GA74495@gweep.net> <16833.7914.394266.619269@ran.psg.com> <8dc5236e0dc3d9b9040f58b9ae907d93@sackheads.org> <16943.22110.100859.97051@roam.psg.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <16943.22110.100859.97051@roam.psg.com> User-Agent: Mutt/1.4.2.1i X-PGP-Key: http://www.gweep.net/~crimson/pgp.txt X-Disclaimer: "I'm the only one foolish enough to claim these opinions." Organization: RSUC: What else do you really need? X-Do-Not-Email-Here: inhuman@place.rsuc.gweep.net X-BeenThere: inet-ops@puck.nether.net X-Mailman-Version: 2.1.6b1 Precedence: list Reply-To: jzp-inetops@rsuc.gweep.net List-Id: list for internet operators List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 May 2005 13:08:05 -0000 On Wed, Mar 09, 2005 at 10:02:38AM -1000, Randy Bush wrote: [snip] > *extremely* initial results, which have now known but minor > errors, were presented at apnic. see > > > > better analysis will be available in a week. Never one to grump at free & meaningful info, I didn't beat the drum on the 'week' marker. Just wondering if there is a horizon to the more detailed/better analysis. > imiho, the bottom line is that anycast amplifies effects of > bgp/igp twitchiness. It is always nice when the gut feeling is confirmed from hard data. Any chance operators [vetted in whatever way you all choose] could get aggregate data from within their AS? or AS + downstreams? Cheers, joe -- RSUC / GweepNet / Spunk / FnB / Usenix / SAGE From randy@psg.com Sun May 1 13:15:20 2005 Received: from rip.psg.com (rip.psg.com [147.28.0.39]) by puck.nether.net (8.13.3/8.12.9) with ESMTP id j41HFJ7A075500 for ; Sun, 1 May 2005 13:15:20 -0400 (EDT) (envelope-from randy@psg.com) X-Envelope-From: randy@psg.com Received: from localhost ([127.0.0.1] helo=roam.psg.com) by rip.psg.com with esmtp (Exim 4.50 (FreeBSD)) id 1DSI2I-000AGx-Pt; Sun, 01 May 2005 17:15:18 +0000 Received: from [127.0.0.1] (helo=roam.psg.com.psg.com) by roam.psg.com with esmtp (Exim 4.50 (FreeBSD)) id 1DSI2C-000ATJ-DR; Sun, 01 May 2005 07:15:12 -1000 From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <17013.3743.908134.52121@roam.psg.com> Date: Sun, 1 May 2005 07:15:11 -1000 To: Joe Provo Subject: Re: [inet-ops] Anycast stability experiment results? References: <20041216045050.GA74495@gweep.net> <16833.7914.394266.619269@ran.psg.com> <8dc5236e0dc3d9b9040f58b9ae907d93@sackheads.org> <16943.22110.100859.97051@roam.psg.com> <20050501130804.GA20062@gweep.net> Cc: inet-ops@puck.nether.net X-BeenThere: inet-ops@puck.nether.net X-Mailman-Version: 2.1.6b1 Precedence: list List-Id: list for internet operators List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 May 2005 17:15:20 -0000 >> better analysis will be available in a week. > Never one to grump at free & meaningful info, I didn't beat > the drum on the 'week' marker. Just wondering if there is a > horizon to the more detailed/better analysis. a bit more is at but there will be more at nanog > Any chance operators [vetted in whatever way you all > choose] could get aggregate data from within their AS? or > AS + downstreams? actually, we are looking for a few good asns to analyse in some depth. what we want is (for you) to run the probe from a few places inside the as while recording as much of the as's internal bgp info as possible in zebra/quagga/mrt format. we believe we will then be able to tell you a bunch about your routing. randy From leo@ripe.net Tue Aug 2 05:17:17 2005 Received: from postman.ripe.net (postman.ripe.net [193.0.0.199]) by puck.nether.net (8.13.4/8.12.9) with ESMTP id j729HGbk095702 for ; Tue, 2 Aug 2005 05:17:17 -0400 (EDT) (envelope-from leo@ripe.net) X-Envelope-From: leo@ripe.net Received: by postman.ripe.net (Postfix, from userid 4008) id 21E3B246E7; Tue, 2 Aug 2005 11:17:11 +0200 (CEST) Received: from birch.ripe.net (birch.ripe.net [193.0.1.96]) by postman.ripe.net (Postfix) with ESMTP id C6CD524606; Tue, 2 Aug 2005 11:17:07 +0200 (CEST) Received: from [IPv6:::1] (cow.ripe.net [193.0.1.239]) by birch.ripe.net (8.12.10/8.11.6) with ESMTP id j729H7mq020235; Tue, 2 Aug 2005 11:17:07 +0200 Mime-Version: 1.0 (Apple Message framework v733) Content-Transfer-Encoding: 7bit Message-Id: Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed To: afnog@afnog.org, nanog@merit.edu, nznog@list.waikato.ac.nz, uknof@ukif.org.uk, sanog@sanog.org, eof-list@ripe.net, inet-ops@puck.nether.net From: leo vegoda Date: Tue, 2 Aug 2005 11:17:05 +0200 X-Mailer: Apple Mail (2.733) X-RIPE-Spam-Level: X-RIPE-Spam-Tests: ALL_TRUSTED,BAYES_00 X-RIPE-Spam-Status: N 0.003657 / -5.9 X-RIPE-Signature: 1f63858b64d9f08866e4778058d77c90 Subject: [inet-ops] RIPE NCC to begin allocating from new IPv4 range X-BeenThere: inet-ops@puck.nether.net X-Mailman-Version: 2.1.6b1 Precedence: list List-Id: list for internet operators List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 Aug 2005 09:17:18 -0000 Dear Colleagues, This announcement is being sent to multiple lists. I apologise for duplicates. The RIPE NCC received the IPv4 address range 89.0.0.0 - 91.255.255.255 (89.0.0.0/8 and 90.0.0.0/7) from the IANA in June 2005. We expect to start making allocations from this range in the near future. We have started announcing two prefixes from each /8, which originate in AS12654. They are: 89.192.0.0/16 89.255.248.0/21 90.192.0.0/16 90.255.248.0/21 91.192.0.0/16 91.255.248.0/21 Details of target names and addresses, reachability tools and other information are available on our web site at: http://www.ris.ripe.net/debogon/debogon.html You may want to update any filters you have in place. Kind regards, -- leo vegoda Registration Services Manager RIPE NCC From randy@psg.com Tue Sep 20 16:37:24 2005 Received: from rip.psg.com (rip.psg.com [147.28.0.39]) by puck.nether.net (8.13.5.Beta0/8.12.9) with ESMTP id j8KKbNZJ002828 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Tue, 20 Sep 2005 16:37:24 -0400 (EDT) (envelope-from randy@psg.com) X-Envelope-From: randy@psg.com Received: from localhost ([127.0.0.1] helo=roam.psg.com) by rip.psg.com with esmtp (Exim 4.51 (FreeBSD)) id 1EHorc-000ACF-Fr; Tue, 20 Sep 2005 20:37:16 +0000 Received: from localhost ([127.0.0.1] helo=roam.psg.com) by roam.psg.com with esmtp (Exim 4.52 (FreeBSD)) id 1EHora-000FmB-R8; Tue, 20 Sep 2005 10:37:14 -1000 From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <17200.29433.730221.627372@roam.psg.com> Date: Tue, 20 Sep 2005 10:37:13 -1000 To: "Leslie Nobile" References: <20050920145149.059861FF33@mercury.arin.net> Cc: nanog@merit.edu, inet-ops@puck.nether.net, uknof@ukif.org.uk, afnog@afnog.org, nznog@list.waikato.ac.nz, eof-list@ripe.net, sanog@sanog.org Subject: [inet-ops] Re: ARIN to allocate from 74/8 & 75/8 X-BeenThere: inet-ops@puck.nether.net X-Mailman-Version: 2.1.6b1 Precedence: list List-Id: list for internet operators List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Sep 2005 20:37:24 -0000 > Connectivity testing is currently being done by Team Cymru on the following > three /20s (one from each /8). All of these test allocations originate with > AS36666. > > 74.63.0.0/20 > 75.127.0.0/20 > 76.191.0.0/20 and how is that testing being done? how do we test that we can reach the prefixes? i.e. is there a pingable address in each, as has been discussed here just a few times? randy From randy@psg.com Tue Sep 20 17:05:39 2005 Received: from rip.psg.com (rip.psg.com [147.28.0.39]) by puck.nether.net (8.13.5.Beta0/8.12.9) with ESMTP id j8KL5dOC007487 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Tue, 20 Sep 2005 17:05:39 -0400 (EDT) (envelope-from randy@psg.com) X-Envelope-From: randy@psg.com Received: from localhost ([127.0.0.1] helo=roam.psg.com) by rip.psg.com with esmtp (Exim 4.51 (FreeBSD)) id 1EHpIy-000AzY-VM; Tue, 20 Sep 2005 21:05:33 +0000 Received: from localhost ([127.0.0.1] helo=roam.psg.com) by roam.psg.com with esmtp (Exim 4.52 (FreeBSD)) id 1EHpIx-000Fri-9l; Tue, 20 Sep 2005 11:05:31 -1000 From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <17200.31129.995766.30582@roam.psg.com> Date: Tue, 20 Sep 2005 11:05:29 -1000 To: "Christopher L. Morrow" References: <20050920145149.059861FF33@mercury.arin.net> <17200.29433.730221.627372@roam.psg.com> <20050920204920.GH5285@renesys.com> X-Mailman-Approved-At: Tue, 20 Sep 2005 17:27:30 -0400 Cc: nanog@merit.edu, inet-ops@puck.nether.net, Leslie Nobile , Todd Underwood , uknof@ukif.org.uk, sanog@sanog.org, nznog@list.waikato.ac.nz, eof-list@ripe.net, afnog@afnog.org Subject: [inet-ops] Re: [afnog] ARIN to allocate from 74/8 & 75/8 X-BeenThere: inet-ops@puck.nether.net X-Mailman-Version: 2.1.6b1 Precedence: list List-Id: list for internet operators List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Sep 2005 21:05:39 -0000 >> if it's useful, i'd be happy to report what percentage of my peers >> have/don't have routes to these prefixes. route-views and ris provide pretty good views of route propagation. but, as you seem to understand, that's only half the story. luckily, the other, more useful, half is easily testable if arin/cymru would just follow the long-discussed path. randy From leo@ripe.net Thu Aug 31 04:53:06 2006 Received: from postman.ripe.net (postman.ripe.net [193.0.0.199]) by puck.nether.net (8.13.7/8.12.9) with ESMTP id k7V8r6gF021399 for ; Thu, 31 Aug 2006 04:53:06 -0400 (EDT) (envelope-from leo@ripe.net) X-Envelope-From: leo@ripe.net Received: by postman.ripe.net (Postfix, from userid 4008) id 9B33124023; Thu, 31 Aug 2006 10:53:00 +0200 (CEST) Received: from herring.ripe.net (herring.ripe.net [193.0.1.203]) by postman.ripe.net (Postfix) with ESMTP id 778172401E; Thu, 31 Aug 2006 10:53:00 +0200 (CEST) Received: from [127.0.0.1] (chimp.ripe.net [193.0.1.199]) by herring.ripe.net (Postfix) with ESMTP id 701172F592; Thu, 31 Aug 2006 10:52:59 +0200 (CEST) Mime-Version: 1.0 (Apple Message framework v752.2) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <5AF59DCD-983F-4C8C-8183-A3D30DDAF14D@ripe.net> Content-Transfer-Encoding: 7bit From: leo vegoda Date: Thu, 31 Aug 2006 10:52:45 +0200 To: Address Policy WG , Routing WG X-Mailer: Apple Mail (2.752.2) X-RIPE-Spam-Level: X-RIPE-Spam-Tests: ALL_TRUSTED,BAYES_00 X-RIPE-Spam-Status: N 0.000052 / -4.4 X-RIPE-Signature: 08c776c1c1b47a992fed1bbba65e2296 Cc: PacNOG List , NANOG List , Inet Ops List , UKNOF List , AfNOG List , NZNOG List , SANOG List Subject: [inet-ops] New IPv4 blocks allocated to RIPE NCC X-BeenThere: inet-ops@puck.nether.net X-Mailman-Version: 2.1.8 Precedence: list List-Id: list for internet operators List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 Aug 2006 08:53:07 -0000 [Apologies for duplicate mails] Dear Colleagues, The RIPE NCC received the IPv4 address ranges 77.0.0.0/8 and 78.0.0.0/7 from the IANA in August 2006. We will begin allocating from these ranges in the near future. The minimum allocation size for these four /8s has been set at /21. You may wish to adjust any filters you have in place accordingly. More information on the IP space administered by the RIPE NCC can be found on our web site at: https://www.ripe.net/ripe/docs/ripe-ncc-managed-address-space.html Additionally, please note that two "pilot" prefixes are being announced from each /8. Details of the prefixes, 'pingable' target names and addresses for each prefix can be found on our web site at: http://www.ris.ripe.net/debogon/debogon.html Best regards, -- leo vegoda Registration Services Manager RIPE NCC From leo@ripe.net Thu Aug 31 05:01:04 2006 Received: from postman.ripe.net (postman.ripe.net [193.0.0.199]) by puck.nether.net (8.13.7/8.12.9) with ESMTP id k7V9140O022472 for ; Thu, 31 Aug 2006 05:01:04 -0400 (EDT) (envelope-from leo@ripe.net) X-Envelope-From: leo@ripe.net Received: by postman.ripe.net (Postfix, from userid 4008) id 0B33A24024; Thu, 31 Aug 2006 11:00:59 +0200 (CEST) Received: from herring.ripe.net (herring.ripe.net [193.0.1.203]) by postman.ripe.net (Postfix) with ESMTP id E5D1D23FFD; Thu, 31 Aug 2006 11:00:58 +0200 (CEST) Received: from [127.0.0.1] (chimp.ripe.net [193.0.1.199]) by herring.ripe.net (Postfix) with ESMTP id DC7C62F592; Thu, 31 Aug 2006 11:00:58 +0200 (CEST) In-Reply-To: <5AF59DCD-983F-4C8C-8183-A3D30DDAF14D@ripe.net> References: <5AF59DCD-983F-4C8C-8183-A3D30DDAF14D@ripe.net> Mime-Version: 1.0 (Apple Message framework v752.2) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: leo vegoda Date: Thu, 31 Aug 2006 11:00:45 +0200 To: Address Policy WG , Routing WG X-Mailer: Apple Mail (2.752.2) X-RIPE-Spam-Level: X-RIPE-Spam-Tests: ALL_TRUSTED,BAYES_00 X-RIPE-Spam-Status: N 0.000571 / -4.4 X-RIPE-Signature: 2c9605a9b75d2ccda0ed73be9e10adb2 Cc: PacNOG List , NANOG List , Inet Ops List , UKNOF List , AfNOG List , NZNOG List , SANOG List Subject: Re: [inet-ops] New IPv4 blocks allocated to RIPE NCC X-BeenThere: inet-ops@puck.nether.net X-Mailman-Version: 2.1.8 Precedence: list List-Id: list for internet operators List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 Aug 2006 09:01:05 -0000 On 31 Aug 2006, at 10:52GMT+02:00, leo vegoda wrote: > [Apologies for duplicate mails] > > Dear Colleagues, > > The RIPE NCC received the IPv4 address ranges 77.0.0.0/8 and > 78.0.0.0/7 > from the IANA in August 2006. We will begin allocating from these > ranges > in the near future. > > The minimum allocation size for these four /8s has been set at /21. > You > may wish to adjust any filters you have in place accordingly. Typo. That's three /8s, not four. Sorry. -- leo vegoda Registration Services Manager RIPE NCC From leo@ripe.net Tue Sep 26 05:42:50 2006 Received: from postman.ripe.net (postman.ripe.net [193.0.0.199]) by puck.nether.net (8.13.7/8.12.9) with ESMTP id k8Q9gnjY036715 for ; Tue, 26 Sep 2006 05:42:49 -0400 (EDT) (envelope-from leo@ripe.net) X-Envelope-From: leo@ripe.net Received: by postman.ripe.net (Postfix, from userid 4008) id 0E03B240BD; Tue, 26 Sep 2006 11:42:44 +0200 (CEST) Received: from herring.ripe.net (herring.ripe.net [193.0.1.203]) by postman.ripe.net (Postfix) with ESMTP id DED1224004; Tue, 26 Sep 2006 11:42:43 +0200 (CEST) Received: from dog.ripe.net (dog.ripe.net [193.0.1.217]) by herring.ripe.net (Postfix) with ESMTP id DC0042F583; Tue, 26 Sep 2006 11:42:43 +0200 (CEST) Received: (from leo@localhost) by dog.ripe.net (8.12.10/8.12.6) id k8Q9gh2E032140; Tue, 26 Sep 2006 11:42:43 +0200 Message-Id: <200609260942.k8Q9gh2E032140@dog.ripe.net> To: afnog@afnog.org, inet-ops@puck.nether.net, ipv6-ops@lists.cluenet.de, nanog@merit.edu From: leo vegoda X-Mailer: BaT/1.23 Sender: RIPE NCC Staff Date: Tue, 26 Sep 2006 11:42:42 +0200 MIME-Version: 1.0 Content-Type: multipart/signed; boundary="----------=_1159263763-31874-0"; micalg="pgp-sha1"; protocol="application/pgp-signature" X-RIPE-Spam-Level: X-RIPE-Spam-Tests: ALL_TRUSTED,BAYES_00 X-RIPE-Spam-Status: N 0.000000 / -4.4 X-RIPE-Signature: 65a5f2d77648cc667111641b6c7c27da Subject: [inet-ops] 2005-02 implementation: IP assignments for anycasting DNS X-BeenThere: inet-ops@puck.nether.net X-Mailman-Version: 2.1.9 Precedence: list Reply-To: leo vegoda List-Id: list for internet operators List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Sep 2006 09:42:50 -0000 This is a cryptographically signed message in MIME format. ------------=_1159263763-31874-0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-length: 763 Dear Colleagues, Following a request, this announcement is being sent to a few ops focused mailing lists. We are pleased to announce that we will be able to accept e-mailed requests for assignments for anycasting DNS servers from 2 October 2006. The request form and supporting notes will be available from the RIPE Document Store at: http://www.ripe.net/ripe/docs/internet-registries.html We will make a separate announcement when it is possible to make requests via the LIR Portal. Assignments for anycasting DNS will come from reserved blocks: * IPv4 Anycast Assignments (/24) from 194.0.0.0/18 * IPv6 Anycast Assignments (/48) from 2001:0678::/29 You may want to update your filters. Regards, --=20 leo vegoda RIPE NCC Registration Services Manager ------------=_1159263763-31874-0 Content-Type: application/pgp-signature Content-Disposition: inline Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- Comment: For info see https://www.ripe.net/rs/pgp/ iD8DBQFFGPYTmbreNIsOKy8RAur4AJ9WxcMCuDFxyekHaAU98LC1feM1KACfUpMn H7LhQdlGnWkCdr0FMkS/9MI= =3cq0 -----END PGP SIGNATURE----- ------------=_1159263763-31874-0-- From leo@ripe.net Wed Oct 18 05:21:47 2006 Received: from postman.ripe.net (postman.ripe.net [193.0.0.199]) by puck.nether.net (8.13.8/8.12.9) with ESMTP id k9I9Lkck000360 for ; Wed, 18 Oct 2006 05:21:46 -0400 (EDT) (envelope-from leo@ripe.net) X-Envelope-From: leo@ripe.net Received: by postman.ripe.net (Postfix, from userid 4008) id E7E4E24358; Wed, 18 Oct 2006 11:21:40 +0200 (CEST) Received: from herring.ripe.net (herring.ripe.net [193.0.1.203]) by postman.ripe.net (Postfix) with ESMTP id C698B24340; Wed, 18 Oct 2006 11:21:40 +0200 (CEST) Received: from [127.0.0.1] (chimp.ripe.net [193.0.1.199]) by herring.ripe.net (Postfix) with ESMTP id BC01E2F583; Wed, 18 Oct 2006 11:21:40 +0200 (CEST) Mime-Version: 1.0 (Apple Message framework v752.3) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <1803697A-F814-4A0F-A3A9-8642A83F0B95@ripe.net> Content-Transfer-Encoding: 7bit From: leo vegoda Date: Wed, 18 Oct 2006 11:21:36 +0200 To: Address Policy WG , Routing WG , IPv6 WG X-Mailer: Apple Mail (2.752.3) X-RIPE-Spam-Level: X-RIPE-Spam-Tests: ALL_TRUSTED,BAYES_00 X-RIPE-Spam-Status: N 0.000005 / -4.4 X-RIPE-Signature: 71ab33516dcc139b6563b5bb85445a60 X-Mailman-Approved-At: Thu, 19 Oct 2006 09:15:05 -0400 Cc: PacNOG List , NANOG List , Inet Ops List , UKNOF List , IPv6 Ops List , AfNOG List , NZNOG List , SANOG List Subject: [inet-ops] New IPv6 block allocated to RIPE NCC X-BeenThere: inet-ops@puck.nether.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: list for internet operators List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 Oct 2006 09:21:49 -0000 [Apologies for duplicate mails] Dear Colleagues, The RIPE NCC received the IPv6 address range 2a00::/12 from the IANA in October 2006. This allocation expands two previous allocations. We will begin allocating from this new space in the near future. The minimum allocation size for this /12 has been set at /32. You may wish to adjust any filters you have in place accordingly. More information on the IP space administered by the RIPE NCC can be found on our web site at: https://www.ripe.net/ripe/docs/ripe-ncc-managed-address-space.html Regards, -- leo vegoda Registration Services Manager RIPE NCC From jared@puck.nether.net Tue Aug 21 15:24:34 2007 Received: from puck.nether.net (puck.nether.net [204.42.254.5]) by puck.nether.net (8.14.1/8.12.9) with ESMTP id l7LJOYwq091747 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Tue, 21 Aug 2007 15:24:34 -0400 (EDT) (envelope-from jared@puck.nether.net) X-Envelope-From: jared@puck.nether.net Received: (from jared@localhost) by puck.nether.net (8.14.1/8.12.9/Submit) id l7LJOYC3091746 for inet-ops@puck.nether.net; Tue, 21 Aug 2007 15:24:34 -0400 (EDT) (envelope-from jared) Date: Tue, 21 Aug 2007 15:24:34 -0400 From: Jared Mauch To: inet-ops@puck.nether.net Message-ID: <20070821192433.GC89691@puck.nether.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.15 (2007-04-06) X-Greylist: Sender is SPF-compliant, not delayed by milter-greylist-4.0a6 (puck.nether.net [204.42.254.5]); Tue, 21 Aug 2007 15:24:34 -0400 (EDT) Subject: [inet-ops] routing leak detection system X-BeenThere: inet-ops@puck.nether.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: list for internet operators List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Aug 2007 19:24:34 -0000 I'm releasing this for semi-public beta. http://puck.nether.net/bgp/leakinfo.cgi This detects routing leaks from major networks or their customers that are not properly filtered. Please send me feedback in private. If you're part of one of the leaks, please look into it and let me know. - Jared -- Jared Mauch | pgp key available via finger from jared@puck.nether.net clue++; | http://puck.nether.net/~jared/ My statements are only mine. From randy@psg.com Tue Aug 21 15:47:22 2007 Received: from rip.psg.com (rip.psg.com [147.28.0.39]) by puck.nether.net (8.14.1/8.12.9) with ESMTP id l7LJlLhJ096484 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Tue, 21 Aug 2007 15:47:22 -0400 (EDT) (envelope-from randy@psg.com) X-Envelope-From: randy@psg.com Received: from cust16202.lava.net ([64.65.95.74] helo=[192.168.0.102]) by rip.psg.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.67 (FreeBSD)) (envelope-from ) id 1INZh5-000CUy-OP; Tue, 21 Aug 2007 19:47:15 +0000 Message-ID: <46CB4132.9090605@psg.com> Date: Tue, 21 Aug 2007 09:46:58 -1000 From: Randy Bush User-Agent: Thunderbird 2.0.0.6 (Windows/20070728) MIME-Version: 1.0 To: Jared Mauch References: <20070821192433.GC89691@puck.nether.net> In-Reply-To: <20070821192433.GC89691@puck.nether.net> X-Enigmail-Version: 0.95.2 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Greylist: IP, sender and recipient auto-whitelisted, not delayed by milter-greylist-4.0a6 (puck.nether.net [204.42.254.5]); Tue, 21 Aug 2007 15:47:22 -0400 (EDT) Cc: inet-ops@puck.nether.net Subject: Re: [inet-ops] routing leak detection system X-BeenThere: inet-ops@puck.nether.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: list for internet operators List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Aug 2007 19:47:23 -0000 this could use a bit more explanation of what you are actually diagnosing and how to read it. randy From leo.vegoda@icann.org Mon Oct 1 06:10:23 2007 Received: from smtp01.icann.org (smtp2.lax.icann.org [208.77.188.15]) by puck.nether.net (8.14.1/8.12.9) with ESMTP id l91AALk9023569 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Mon, 1 Oct 2007 06:10:23 -0400 (EDT) (envelope-from leo.vegoda@icann.org) X-Envelope-From: leo.vegoda@icann.org Received: from [213.246.198.37] ([213.246.198.37]) (authenticated bits=0) by smtp01.icann.org (8.13.8/8.12.11) with ESMTP id l919Ubma005196 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Mon, 1 Oct 2007 02:30:39 -0700 Mime-Version: 1.0 (Apple Message framework v752.3) X-Gpgmail-State: !encrypted,!signed Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <3F6D6D6F-1EB8-452C-B4ED-3E2702D8360E@icann.org> Content-Transfer-Encoding: 7bit From: Leo Vegoda Date: Mon, 1 Oct 2007 11:30:36 +0200 To: Leo Vegoda X-Mailer: Apple Mail (2.752.3) X-Greylist: Delayed for 00:39:05 by milter-greylist-4.0b2 (puck.nether.net [204.42.254.5]); Mon, 01 Oct 2007 06:10:23 -0400 (EDT) X-Mailman-Approved-At: Mon, 01 Oct 2007 06:59:15 -0400 Subject: [inet-ops] 186/8 and 187/8 allocated to LACNIC X-BeenThere: inet-ops@puck.nether.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: list for internet operators List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 01 Oct 2007 10:10:23 -0000 Hi, The IANA IPv4 registry has been updated to reflect the allocation of two /8 IPv4 blocks to LACNIC in September 2007: 186/8 and 187/8. You can find the IANA IPv4 registry at: http://www.iana.org/assignments/ipv4-address-space Please update your filters as appropriate. Regards, -- Leo Vegoda Manager, Number Resources - IANA From leo.vegoda@icann.org Mon Oct 29 11:45:03 2007 Received: from smtp01.icann.org (smtp1.lax.icann.org [208.77.188.14]) by puck.nether.net (8.14.1/8.12.9) with ESMTP id l9TFj1ls091222 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Mon, 29 Oct 2007 11:45:02 -0400 (EDT) (envelope-from leo.vegoda@icann.org) X-Envelope-From: leo.vegoda@icann.org Received: from [8.193.45.234] (8-193-45-234.losangeles.icannmeeting.org [8.193.45.234]) (authenticated bits=0) by smtp01.icann.org (8.13.8/8.12.11) with ESMTP id l9TFi86A004434 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Mon, 29 Oct 2007 08:44:08 -0700 Mime-Version: 1.0 (Apple Message framework v752.3) Content-Transfer-Encoding: 7bit Message-Id: <4252C148-4F85-4DDD-B138-028D56A2CF31@icann.org> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed To: AfNOG , AusNOG , CaribNOG , Inet-Ops , JaNOG , NANOG , NZNOG , PACNOG , SANOG , UKNOF From: Leo Vegoda Date: Mon, 29 Oct 2007 16:44:06 +0100 X-Mailer: Apple Mail (2.752.3) X-Greylist: IP, sender and recipient auto-whitelisted, not delayed by milter-greylist-4.0rc2 (puck.nether.net [204.42.254.5]); Mon, 29 Oct 2007 11:45:03 -0400 (EDT) X-Mailman-Approved-At: Mon, 29 Oct 2007 11:47:06 -0400 Subject: [inet-ops] 114/8 and 115/8 allocated to APNIC X-BeenThere: inet-ops@puck.nether.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: list for internet operators List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Oct 2007 15:45:07 -0000 Hi, The IANA IPv4 registry has been updated to reflect the allocation of two /8 IPv4 blocks to APNIC in October 2007: 144/8 and 115/8. You can find the IANA IPv4 registry at: http://www.iana.org/assignments/ipv4-address-space Please update your filters as appropriate. Regards, Leo vegoda Manager, Number Resources - IANA From leo.vegoda@icann.org Mon Oct 29 12:16:38 2007 Received: from smtp01.icann.org (smtp2.lax.icann.org [208.77.188.15]) by puck.nether.net (8.14.1/8.12.9) with ESMTP id l9TGGbTK017046 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Mon, 29 Oct 2007 12:16:38 -0400 (EDT) (envelope-from leo.vegoda@icann.org) X-Envelope-From: leo.vegoda@icann.org Received: from [8.193.45.234] (8-193-45-234.losangeles.icannmeeting.org [8.193.45.234]) (authenticated bits=0) by smtp01.icann.org (8.13.8/8.12.11) with ESMTP id l9TGG6Gm011564 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Mon, 29 Oct 2007 09:16:07 -0700 Mime-Version: 1.0 (Apple Message framework v752.3) In-Reply-To: <4252C148-4F85-4DDD-B138-028D56A2CF31@icann.org> References: <4252C148-4F85-4DDD-B138-028D56A2CF31@icann.org> X-Gpgmail-State: !signed Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <6A194BE6-3B92-482C-B4A3-9FB9918406E7@icann.org> Content-Transfer-Encoding: 7bit From: Leo Vegoda Date: Mon, 29 Oct 2007 17:16:04 +0100 To: AfNOG , AusNOG , CaribNOG , Inet-Ops , JaNOG , NANOG list , NZNOG , PACNOG , SANOG , UKNOF X-Mailer: Apple Mail (2.752.3) X-Greylist: IP, sender and recipient auto-whitelisted, not delayed by milter-greylist-4.0rc2 (puck.nether.net [204.42.254.5]); Mon, 29 Oct 2007 12:16:38 -0400 (EDT) X-Mailman-Approved-At: Mon, 29 Oct 2007 14:08:14 -0400 Subject: Re: [inet-ops] 114/8 and 115/8 allocated to APNIC X-BeenThere: inet-ops@puck.nether.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: list for internet operators List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Oct 2007 16:16:38 -0000 On 29 Oct 2007, at 16:44, Leo Vegoda wrote: > The IANA IPv4 registry has been updated to reflect the allocation of > two /8 IPv4 blocks to APNIC in October 2007: 144/8 and 115/8. You can > find the IANA IPv4 registry at: I made a typo in the body of this mail. APNIC was allocated 114/8 and not 144/8. Sorry for any confusion. Leo From leo.vegoda@icann.org Thu Feb 14 14:52:38 2008 Received: from EXHUB016-4.exch016.msoutlookonline.net (exhub016-4.exch016.msoutlookonline.net [207.5.72.225]) by puck.nether.net (8.14.2/8.12.9) with ESMTP id m1EJqbPO081559 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=FAIL) for ; Thu, 14 Feb 2008 14:52:37 -0500 (EST) (envelope-from leo.vegoda@icann.org) X-Envelope-From: leo.vegoda@icann.org Received: from EXVMBX016-2.exch016.msoutlookonline.net ([207.5.72.172]) by EXHUB016-4.exch016.msoutlookonline.net ([207.5.72.225]) with mapi; Thu, 14 Feb 2008 11:22:26 -0800 From: Leo Vegoda To: afnog , "ausnog@ausnog.net" , "caribnog@caribnog.net" , "inet-ops@puck.nether.net" , "lacnog@lacnic.net" , "menog@menog.net" , nanog , "nznog@list.waikato.ac.nz" , "pacnog@pacnog.org" , "sanog@sanog.org" , "uknof@uknof.org.uk" , JaNOG Date: Thu, 14 Feb 2008 11:22:21 -0800 Thread-Topic: 173/8 and 174/8 allocated to ARIN Thread-Index: AchvPuuDGzVwSueNrUSMGIckPrb7Lw== Message-ID: Accept-Language: en-US Content-Language: en X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Greylist: Delayed for 00:30:10 by milter-greylist-4.0 (puck.nether.net [204.42.254.5]); Thu, 14 Feb 2008 14:52:38 -0500 (EST) X-Mailman-Approved-At: Thu, 14 Feb 2008 16:34:22 -0500 Subject: [inet-ops] 173/8 and 174/8 allocated to ARIN X-BeenThere: inet-ops@puck.nether.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: list for internet operators List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Feb 2008 19:52:39 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The IANA IPv4 registry has been updated to reflect the allocation of two /8 IPv4 blocks to ARIN in February 2008: 173/8 and 174/8. You can find the IANA IPv4 registry at: http://www.iana.org/assignments/ipv4-address-space Please update your filters as appropriate. Kind regards, Leo Vegoda Manager, Number Resources - IANA -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (Darwin) iD8DBQFHtItTvBLymJnAzRwRAq4hAJsF7zELnkKFSHvGccPpoCK+ypwOLgCfZYgA YJOrIPDwVY2rkq7tQ+wXPAo=3D =3DAme2 -----END PGP SIGNATURE----- From leo.vegoda@icann.org Thu Feb 21 15:55:35 2008 Received: from EXHUB016-1.exch016.msoutlookonline.net (exhub016-1.exch016.msoutlookonline.net [207.5.72.163]) by puck.nether.net (8.14.2/8.12.9) with ESMTP id m1LKtY0Q076364 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=FAIL) for ; Thu, 21 Feb 2008 15:55:34 -0500 (EST) (envelope-from leo.vegoda@icann.org) X-Envelope-From: leo.vegoda@icann.org Received: from EXVMBX016-2.exch016.msoutlookonline.net ([207.5.72.172]) by EXHUB016-1.exch016.msoutlookonline.net ([207.5.72.163]) with mapi; Thu, 21 Feb 2008 12:25:22 -0800 From: Leo Vegoda To: Leo Vegoda Date: Thu, 21 Feb 2008 12:25:17 -0800 Thread-Topic: =?iso-8859-1?Q?Update_to_the_IPv4_Registry=B9s_Format_and_Content?= Thread-Index: Ach0x98T6bSEyvaOvUGgEUKIcNS4Qw== Message-ID: Accept-Language: en-US Content-Language: en X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Greylist: Delayed for 00:30:11 by milter-greylist-4.0 (puck.nether.net [204.42.254.5]); Thu, 21 Feb 2008 15:55:35 -0500 (EST) X-Mailman-Approved-At: Thu, 21 Feb 2008 15:57:44 -0500 Subject: [inet-ops] =?iso-8859-1?q?Update_to_the_IPv4_Registry=B9s_Format_?= =?iso-8859-1?q?and_Content?= X-BeenThere: inet-ops@puck.nether.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: list for internet operators List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Feb 2008 20:55:36 -0000 This message has been sent to several lists. I apologise for duplicates. IANA has improved the format for the IPv4 Address Space registry. At the same time, the entries that were marked =B3Various Registries=B2 have been replaced with references to the Regional Internet Registry (RIR) that provides WHOIS and reverse DNS service for that /8 allocation. If you want to machine-process the IPv4 registry, the new fields are: * Prefix * Designation * Date * Whois * Status * Note where the Date will always be of the form =B3YYYY-MM=B2 and the status has = the following possible values: RESERVED, LEGACY, ALLOCATED and UNALLOCATED /8 allocations that contain legacy assignments in them that are now managed by the RIRs have the text =B3Administered by=B2 in the Designation column. Legacy assignments refer to IP address allocations made before the RIR system was established. Reserved address space held by IANA does not have a date listed. The registry can be found at: http://www.iana.org/assignments/ipv4-address-space If you have questions about the structure of the new format, please send e-mail to iana@iana.org. Kind regards, Leo Vegoda Manager, Number Resources - IANA From leo.vegoda@icann.org Thu May 29 08:31:14 2008 Received: from EXPFE100-1.exc.icann.org (expfe100-1.exc.icann.org [64.78.22.236]) by puck.nether.net (8.14.2/8.12.9) with ESMTP id m4TCVEHU086861 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=FAIL) for ; Thu, 29 May 2008 08:31:14 -0400 (EDT) (envelope-from leo.vegoda@icann.org) X-Envelope-From: leo.vegoda@icann.org Received: from EXVPMBX100-1.exc.icann.org ([64.78.22.233]) by EXPFE100-1.exc.icann.org ([64.78.22.236]) with mapi; Thu, 29 May 2008 04:57:27 -0700 From: Leo Vegoda To: Leo Vegoda Date: Thu, 29 May 2008 04:57:24 -0700 Thread-Topic: 112/8 and 113/8 allocated to APNIC Thread-Index: AcjBgyg8cZFlKQA4PkiUi3WjX9ROJQ== Message-ID: Accept-Language: en-US Content-Language: en X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Greylist: Delayed for 00:30:24 by milter-greylist-4.0 (puck.nether.net [204.42.254.5]); Thu, 29 May 2008 08:31:14 -0400 (EDT) X-Mailman-Approved-At: Sat, 31 May 2008 08:02:33 -0400 Subject: [inet-ops] 112/8 and 113/8 allocated to APNIC X-BeenThere: inet-ops@puck.nether.net X-Mailman-Version: 2.1.10 Precedence: list List-Id: list for internet operators List-Unsubscribe: