- Test - lists.nanog.org

ATT Postmaster Contact
by Robert Webb 18 Mar '14

18 Mar '14

Anyone have a contact for postmaster at att.net? I have one user on an email list I send to and they are blocking for abuse. This list might get 15 email a month that go out. Filled out their "form" but would like to get this resolved in less than "2 days" as they state. Robert

3 3

Re: How to catch a cracker in the US?
by Larry Sheldon 18 Mar '14

18 Mar '14

On 3/17/2014 9:10 PM, shawn wilson wrote: > The point is that 'computer security' involves innovation as much as > is done at hacker spaces (which can be geared to hardware or computer > security or whatever). I think the difference you're trying to argue > is the legality and not the task or process. I think calling the > illegal form of the study of computer security "cracking", the legal > form "hacking" and people who are "cracking" who don't know what > they're doing "script kiddies" is irrelevant, useless, and causes > useless debates (that I started) like this. SSSSCOOOOOOOOORRRRRRE! -- Requiescas in pace o email Two identifying characteristics of System Administrators: Ex turpi causa non oritur actio Infallibility, and the ability to learn from their mistakes. (Adapted from Stephen Pinker)

1 0

Re: How to catch a cracker in the US?
by Larry Sheldon 18 Mar '14

18 Mar '14

On 3/13/2014 8:22 AM, Sholes, Joshua wrote: > On 3/13/14, 12:35 AM, "shawn wilson" <ag4ve.us(a)gmail.com> wrote: >> A note on terminology - whether you know what you're doing, actually break >> into a system, or obtain a thumb drive with data that you weren't supposed >> to have - it has the same end so I'd refer to it by the same term - >> hacking. Trying to differentiate terms based on skill, target, or data >> type is kinda dumb. > > If one came up in this field with a mentor who was old school, or if one > is old school oneself, one tends use the original (as I understand it) > definitions--a "cracker" breaks security or obtains data unlawfully, a > "hacker" is someone who likes ethically playing (in the "joyful > exploration" sense) with complicated systems. > > People who are culturally younger tend use "hacker", as you are doing, for > the former and as far as I can tell no specific term for the latter. > > If you ask me, this is something of a cultural loss. Not sure I can agree with that. I have been in this game for a very long time, but for most of it in places where the world's population cleaved neatly into two parts: "Authorized Users" who could be identified by the facts that they had ID cards, Badges, and knew the door code; and "trespassers" who were all others. Then you new kids came along and (pointlessly, in my opinion) divided the later group into the two described above. -- Requiescas in pace o email Two identifying characteristics of System Administrators: Ex turpi causa non oritur actio Infallibility, and the ability to learn from their mistakes. (Adapted from Stephen Pinker)

4 4

Last Call and Draft program for RIPE 68
by Filiz Yilmaz 17 Mar '14

17 Mar '14

Dear Colleagues, A list of currently accepted RIPE 68 presentations is now published at: https://ripe68.ripe.net/programme/meeting-plan/draft/ There are still few slots remaining for a final RIPE 68 programme and RIPE Programme Committee will accept new proposals until 6 April 2014. This is our last call for you to submit your proposals. Kind regards Filiz Yilmaz Chair, RIPE Programme Committee Begin forwarded message: > From: Filiz Yilmaz <koalafil(a)gmail.com> > Subject: Call for Presentations RIPE 68 > Date: 19 Nov 2013 19:04:34 GMT+1 > To: ripe-list(a)ripe.net, "nanog(a)nanog.org" <nanog(a)nanog.org> > Cc: "pc(a)ripe.net Committee" <pc(a)ripe.net> > > > Dear colleagues, > > Please find the CFP for RIPE 68 below or at https://ripe68.ripe.net/submit-topic/cfp/. > > The deadline for submissions is 2 March 2014. > Please also note that speakers do not receive any extra reduction or funding towards the meeting fee at the RIPE Meetings. > > Kind regards > > Filiz Yilmaz > RIPE PC Chair > http://www.ripe.net/ripe/meetings/ripe-meetings/pc > > > --------------------- > > Call for Presentations > > A RIPE Meeting is an open event where Internet Service Providers, network operators and other interested parties get together. Although the meeting is mostly technical, it is also a chance for people to meet and network with others in their field. > > RIPE 68 will take place from 12 – 16 May 2014 in Warsaw, Poland. > > The RIPE Programme Committee (PC) is now seeking content proposals from the RIPE community for the plenary session presentations, BoFs (Birds of a Feather sessions), panels, workshops, tutorials and lightning talks at RIPE 68. The PC is looking for presentations covering topics of network engineering and operations, including but not limited to: > > • IPv6 deployment > • Managing IPv4 scarcity in operations > • Commercial transactions of IPv4 addresses > • Data centre technologies > • Network and DNS operations > • Internet governance and regulatory practices > • Network and routing security > • Content delivery > • Internet peering and mobile data exchange > > Submissions > > RIPE Meeting attendees are quite sensitive to keeping presentations non-commercial, and product marketing talks are strongly discouraged. Repeated audience feedback shows that the most successful talks focus on operational experience, research results, or case studies. For example, presenters wishing to describe a commercial solution should focus on the underlying technology and not attempt a product demonstration. > > The RIPE PC accepts proposals for different presentation formats, including plenary session presentations, tutorials, workshops, BoFs (Birds of a Feather sessions) and lightning talks. See the full descriptions of these formats at > https://ripe68.ripe.net/submit-topic/presentation-formats/ > > Presenters who are proposing a panel or BoF are encouraged to include speakers from several (perhaps even competing) companies and/or a neutral facilitator. > > In addition to presentations selected in advance for the plenary, the RIPE PC also offers several time slots for “lightning talks”, which are selected immediately before or during the conference. > > The following general requirements apply: > > - Proposals for plenary session presentations, BoFs, panels, workshops and tutorials must be submitted for full consideration no later than 2 March 2014, using the meeting submission system at https://ripe68.ripe.net/submit-topic/guidelines/. Proposals submitted after this date will be considered on a space-available basis. > > - Lightning talks should also be submitted using the meeting submission system (https://ripe68.ripe.net/submit-topic/submission-form/) and can be submitted just days before the RIPE Meeting starts or even during the meeting week. The allocation of lightning talk slots will be announced in short notice – in some cases on the same day but often one day prior to the relevant session. > > - Presenters should indicate how much time they will require. > See more information on time slot allocations per presentation format at https://ripe68.ripe.net/submit-topic/presentation-formats/ > > - Proposals for talks will only be considered by the PC if they contain at least draft presentation slides (slides may be updated later on). For panels, proposals must contain a clear description, as well as the names of invited panelists, presenters and moderators. > > - Due to potential technical issues, it is expected that most, if not all, presenters/panelists will be physically present at the RIPE Meeting. > > If you have any questions or requests concerning content submissions, please email pc [at] ripe [dot] net. > > --------------------- > >

1 0

Re: [dns-wg] Global Vs local node data in www.root-servers.org
by Joe Abley 17 Mar '14

17 Mar '14

On 17 Mar 2014, at 7:39, John Bond <john.bond(a)icann.org> wrote: > Global and Local nodes are very loosely defined terms. However general > consensus of a local node is one that has a desired routing policy which > does not allow the service supernets to propagate globally. As we impose > no policy we mark all nodes as global. I think the taxonomy is probably my fault. At least, I thought I invented it when I wrote http://ftp.isc.org/isc/pubs/tn/isc-tn-2003-1.txt the pertinent text of which is this: Two classes of node are described in this document: Global Nodes advertise their service supernets such that they are propagated globally through the routing system (i.e. they advertise them for transit), and hence potentially provide service for the entire Internet. Local Nodes advertise their service supernets such that the radius of propagation in the routing system is limited, and hence provide service for a contained local catchment area. Global Nodes provide a baseline degree of proximity to the entire Internet. Multiple global nodes are deployed to ensure that the general availability of the service does not rely on the availability or reachability of a single global node. Local Nodes provide contained regions of optimisation. Clients within the catchment area of a local node may have their queries serviced by a Local Node, rather than one of the Global Nodes. The operational considerations that you mention would have been great for me to think about when I wrote that text (i.e. it's the intention of the originator of the route that's important, not the practical limit to propagation of the route due to the policies of other networks). We did a slightly better job in RFC 4768 (e.g. "in such a way", "potentially"): Local-Scope Anycast: reachability information for the anycast Service Address is propagated through a routing system in such a way that a particular anycast node is only visible to a subset of the whole routing system. Local Node: an Anycast Node providing service using a Local-Scope Anycast Address. Global-Scope Anycast: reachability information for the anycast Service Address is propagated through a routing system in such a way that a particular anycast node is potentially visible to the whole routing system. Global Node: an Anycast Node providing service using a Global-Scope Anycast Address. Joe

3 3

How to catch a cracker in the US?
by Markus 17 Mar '14

17 Mar '14

Hi, I'm an ISP in Germany and a cracker (not a hacker :) ) has targeted a customers of mine in the last days. The cracker was successful and caused financial damage / was successful with data theft. I set a trap and finally caught his real IP address - a Comcast user in the US (100% not a proxy or bot). What would be the next steps to pursuit him? If I contact local authorities here in Germany I'm afraid months will pass by and Comcast will have possible already deleted their logs by then (?). Any advice? Thank you! Markus

20 28

Re: US to relinquish control of Internet
by Larry Sheldon 16 Mar '14

16 Mar '14

On 3/15/2014 7:39 AM, Bob Evans wrote: >> It's nice of the DoC to "relinquish" control, but I really don't see it >> changing much other than quieting down some hype from countries that were >> saying they were pissed at the US for "controlling" the Internet. And I >> couldn't really see those countries doing anything about it unless the US >> did something actually bad, which they wouldn't do IMHO. >> >> Was I being a pollyanna? > > Yep, way to optimistic. The world always wants the success of capitalism > as long as they don't have to create the climate for it, they just want it > handed to them. Once they have it they turn it back toward socialism and > proceed to F%^$ it up. Gee, sound like the direction our system's been > trying to go in for the last 6 years. Or 101 years. -- Requiescas in pace o email Two identifying characteristics of System Administrators: Ex turpi causa non oritur actio Infallibility, and the ability to learn from their mistakes. (Adapted from Stephen Pinker)

2 1

Global Vs local node data in www.root-servers.org
by Anurag Bhatia 16 Mar '14

16 Mar '14

Hello everyone! It seems like http://www.root-servers.org/index.html has been updated after quite sometime. Seems like data about local Vs global for many of root servers nodes is incorrect. E.g for Netnod i root all nodes are marked as Global nodes. As far as I understand it means that routes announced by these nodes are announced to transit links as well to make routes visible globally. Likely that is not case here right? Same seems with L root and few others. Do we have webmaster of the project on mailing list? Thanks. -- Anurag Bhatia anuragbhatia.com Linkedin <http://in.linkedin.com/in/anuragbhatia21> | Twitter<https://twitter.com/anurag_bhatia> Skype: anuragbhatia.com PGP Key Fingerprint: 3115 677D 2E94 B696 651B 870C C06D D524 245E 58E2

2 1

Verizon FIOS issues in the Washington DC issue with HTTPS traffic?
by Ulf Zimmermann 15 Mar '14

15 Mar '14

We have a number of customers in the DC area on Verizon Fios who can talk to us using http, but not https. Linkedin also tweeted there are issues via Verzion Fios. Verizon support so far denies everything. Anyone else seeing issues? -- Ulf Zimmermann, 1525 Pacific Ave., Alameda, CA-94501, #: 510-396-1764 You can find my resume at: http://www.Alameda.net/~ulf/resume.html

3 2

BGP Update Report
by cidr-report＠potaroo.net 14 Mar '14

14 Mar '14

BGP Update Report Interval: 06-Mar-14 -to- 13-Mar-14 (7 days) Observation Point: BGP Peering with AS131072 TOP 20 Unstable Origin AS Rank ASN Upds % Upds/Pfx AS-Name 1 - AS29571 48376 2.4% 267.3 -- CITelecom-AS 2 - AS10620 36314 1.8% 14.4 -- Telmex Colombia S.A. 3 - AS8402 34000 1.6% 22.1 -- CORBINA-AS OJSC "Vimpelcom" 4 - AS9829 32270 1.6% 36.9 -- BSNL-NIB National Internet Backbone 5 - AS39382 30104 1.5% 15052.0 -- TRANCETELECOM-AS Trance Telecom Inc 6 - AS28573 28211 1.4% 15.0 -- NET Serviços de Comunicação S.A. 7 - AS13118 22545 1.1% 805.2 -- ASN-YARTELECOM OJSC Rostelecom 8 - AS25184 22283 1.1% 184.2 -- AFRANET AFRANET Co. Tehran, Iran 9 - AS17974 21353 1.0% 7.8 -- TELKOMNET-AS2-AP PT Telekomunikasi Indonesia 10 - AS41691 19792 1.0% 1799.3 -- SUMTEL-AS-RIPE Summa Telecom LLC 11 - AS4775 17846 0.9% 557.7 -- GLOBE-TELECOM-AS Globe Telecoms 12 - AS23893 14605 0.7% 374.5 -- BPL-BD House No:03, Road no: 23/A 13 - AS8151 13801 0.7% 18.1 -- Uninet S.A. de C.V. 14 - AS24323 12780 0.6% 206.1 -- AAMRA-NETWORKS-AS-AP aamra networks limited, 15 - AS11976 12383 0.6% 1375.9 -- FIDN - Fidelity Communication International Inc. 16 - AS647 12202 0.6% 111.9 -- DNIC-ASBLK-00616-00665 - DoD Network Information Center 17 - AS45899 11239 0.5% 28.7 -- VNPT-AS-VN VNPT Corp 18 - AS6629 10704 0.5% 164.7 -- NOAA-AS - NOAA 19 - AS7552 10632 0.5% 9.6 -- VIETEL-AS-AP Viettel Corporation 20 - AS28024 10010 0.5% 14.6 -- Nuevatel PCS de Bolivia S.A. TOP 20 Unstable Origin AS (Updates per announced prefix) Rank ASN Upds % Upds/Pfx AS-Name 1 - AS39382 30104 1.5% 15052.0 -- TRANCETELECOM-AS Trance Telecom Inc 2 - AS6459 7806 0.4% 7806.0 -- TRANSBEAM - I-2000, Inc. 3 - AS47033 6544 0.3% 3272.0 -- BASENINE-RIVERSIDE - BaseNine, Inc. 4 - AS54465 8433 0.4% 2811.0 -- QPM-AS-1 - QuickPlay Media Inc. 5 - AS59217 2376 0.1% 2376.0 -- AZONNELIMITED-AS-AP Azonne Limited 6 - AS37367 1866 0.1% 1866.0 -- CALLKEY 7 - AS41691 19792 1.0% 1799.3 -- SUMTEL-AS-RIPE Summa Telecom LLC 8 - AS16561 3019 0.1% 1509.5 -- ARIBANETWORK Ariba Inc. Autonomous System 9 - AS3 1454 0.1% 3297.0 -- MIT-GATEWAYS - Massachusetts Institute of Technology 10 - AS11976 12383 0.6% 1375.9 -- FIDN - Fidelity Communication International Inc. 11 - AS18135 8937 0.4% 1276.7 -- BTV BTV Cable television 12 - AS45924 1092 0.1% 1092.0 -- GLOBAL-AS-AP Global Technologies Limited 13 - AS34912 4326 0.2% 1081.5 -- IFN-AS INTERFUSION INET AS 14 - AS59606 935 0.1% 935.0 -- IT-SVYAZ-SERVICE-AS IT Svyaz Service Ltd. 15 - AS14340 1758 0.1% 879.0 -- SALESFORCE - Salesforce.com, Inc. 16 - AS53041 838 0.0% 838.0 -- Infoclique Telecomunicacoes Ltda Me 17 - AS13118 22545 1.1% 805.2 -- ASN-YARTELECOM OJSC Rostelecom 18 - AS57201 776 0.0% 776.0 -- EDF-AS Estonian Defence Forces 19 - AS62431 722 0.0% 722.0 -- NCSC-IE-AS National Cyber Security Centre 20 - AS20450 1359 0.1% 679.5 -- THL16-ASN - Trojan Hosting, LLC. TOP 20 Unstable Prefixes Rank Prefix Upds % Origin AS -- AS Name 1 - 109.161.64.0/20 22463 1.0% AS13118 -- ASN-YARTELECOM OJSC Rostelecom 2 - 89.221.206.0/24 19739 0.9% AS41691 -- SUMTEL-AS-RIPE Summa Telecom LLC 3 - 195.178.105.0/24 15052 0.7% AS39382 -- TRANCETELECOM-AS Trance Telecom Inc 4 - 195.178.104.0/24 15052 0.7% AS39382 -- TRANCETELECOM-AS Trance Telecom Inc 5 - 192.58.232.0/24 10576 0.5% AS6629 -- NOAA-AS - NOAA 6 - 78.109.192.0/20 9911 0.5% AS25184 -- AFRANET AFRANET Co. Tehran, Iran 7 - 216.109.107.0/24 9783 0.4% AS11486 -- COLO-PREM-VZB - Verizon Online LLC AS16561 -- ARIBANETWORK Ariba Inc. Autonomous System 8 - 42.83.48.0/20 8925 0.4% AS18135 -- BTV BTV Cable television 9 - 120.28.62.0/24 8896 0.4% AS4775 -- GLOBE-TELECOM-AS Globe Telecoms 10 - 222.127.0.0/24 8711 0.4% AS4775 -- GLOBE-TELECOM-AS Globe Telecoms 11 - 206.152.15.0/24 8421 0.4% AS54465 -- QPM-AS-1 - QuickPlay Media Inc. 12 - 205.247.12.0/24 7806 0.3% AS6459 -- TRANSBEAM - I-2000, Inc. 13 - 200.23.126.0/24 7658 0.3% AS8151 -- Uninet S.A. de C.V. 14 - 103.11.61.0/24 7634 0.3% AS9387 -- AUGERE-PK AUGERE-Pakistan 15 - 67.210.190.0/23 7333 0.3% AS11976 -- FIDN - Fidelity Communication International Inc. 16 - 67.210.188.0/23 5035 0.2% AS11976 -- FIDN - Fidelity Communication International Inc. 17 - 121.52.144.0/24 4619 0.2% AS17557 -- PKTELECOM-AS-PK Pakistan Telecommunication Company Limited AS45773 -- HECPERN-AS-PK PERN AS Content Servie Provider, Islamabad, Pakistan 18 - 5.150.145.0/24 4283 0.2% AS34912 -- IFN-AS INTERFUSION INET AS 19 - 199.187.118.0/24 3745 0.2% AS11054 -- LIVEPERSON LivePerson, Inc 20 - 2.93.235.0/24 3434 0.2% AS8402 -- CORBINA-AS OJSC "Vimpelcom" Details at http://bgpupdates.potaroo.net ------------------------------------ Copies of this report are mailed to: nanog(a)nanog.org eof-list(a)ripe.net apops(a)apops.net routing-wg(a)ripe.net afnog(a)afnog.org

1 0