- ripe-list - mailman.ripe.net

RE: look for BGP routes containing local AS#
by Jamie Stallwood 27 Jan '15

27 Jan '15

This can happen. Say you are AS1. You have an end customer on AS2 and peer with core sites AS3 and AS4. From the link to AS4 you may see your customer prefixes with the path 3,4,1,2. -- Jamie Stallwood Security Specialist Imerja Limited M: 07795 840385 Sent from mobile secured by Good (www.good.com) -----Original Message----- From: Song Li [refresh.lsong(a)gmail.com] Sent: Tuesday, January 27, 2015 02:24 PM GMT Standard Time To: carlos(a)lacnic.net; ripe-list(a)ripe.net Subject: Re: look for BGP routes containing local AS# not necessary, it can appear in any place in the received AS-PATH. regards Song 在 2015/1/27 22:20, Carlos M. Martinez 写道: > Is 'local as' the same as the origin-as ? That is, the first item in the > AS-PATH list ? > > regards > > Carlos > > On 1/27/15 12:16 PM, Song Li wrote: >> For example, My AS# is 23910 and the 'local AS' is 23910. If our BGP >> router received a route from the BGP neighbor AS1 with the AS-PATH: 1 .* >> 23910, then the route is what we are looking for. >> >> 在 2015/1/27 22:05, Carlos M. Martinez 写道: >>> Can you clarify what do you mean by 'local AS' ? >>> >>> regards >>> >>> Carlos >>> >>> On 1/27/15 11:48 AM, Song Li wrote: >>>> Hi everyone, >>>> >>>> Recently I studied the BGP AS path looping problem, and found that in >>>> most cases, the received BGP routes containing local AS# are suspicious. >>>> However, we checked our BGP routing table (AS23910,CERNET2) on juniper >>>> router(show route hidden terse aspath-regex .*23910.* ), and have not >>>> found such routes in Adj-RIB-In. >>>> >>>> We believe that the received BGP routes containing local AS# are related >>>> to BGP security problem. Hence, we want to look for some real cases in >>>> the wild. Could anybody give us some examples of such routes? >>>> >>>> Thanks! >>>> >>>> Best Regards! >>>> >> >> -- Song Li Room 4-204, FIT Building, Network Security, Department of Electronic Engineering, Tsinghua University, Beijing 100084, China Tel:( +86) 010-62446440 E-mail: refresh.lsong(a)gmail.com

1 0

look for BGP routes containing local AS#
by Song Li 27 Jan '15

27 Jan '15

Hi everyone, Recently I studied the BGP AS path looping problem, and found that in most cases, the received BGP routes containing local AS# are suspicious. However, we checked our BGP routing table (AS23910,CERNET2) on juniper router(show route hidden terse aspath-regex .*23910.* ), and have not found such routes in Adj-RIB-In. We believe that the received BGP routes containing local AS# are related to BGP security problem. Hence, we want to look for some real cases in the wild. Could anybody give us some examples of such routes? Thanks! Best Regards! -- Song Li Room 4-204, FIT Building, Network Security, Department of Electronic Engineering, Tsinghua University, Beijing 100084, China Tel:( +86) 010-62446440 E-mail: refresh.lsong(a)gmail.com

2 4

SEE 4/RIPE NCC Regional Meeting: Registration Open!
by SEE 26 Jan '15

26 Jan '15

Dear colleagues, The fourth RIPE NCC Regional Meeting/South East Europe Meeting (SEE 4) takes places in Belgrade at the Metropol Palace Hotel on 21-22 April 2015. Join us there! The SEE 4/RIPE NCC Regional Meeting is open to everyone and attendance is free of charge. You can register for this meeting at: http://www.ripe.net/see-4/registration This meeting will build on the success of past meetings, which took place in Dubrovnik, Skopje and Sofia. These meetings demonstrated how vibrant the Internet community in the region is, as well as the knowledge-sharing and network-building benefits to be gained from meeting as a community. The meeting will cover a wide range of topics, including: - 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 - Efforts to establish IXPs in the region - Reports from existing IXPs - Regional success stories - Much, much more! Do you have expertise on some of these topics? An interesting case to share with your peers? Then please submit a presentation proposal here: https://www.ripe.net/ripe/meetings/regional-meetings/see-4/cfp Further information about the meeting can be found at: http://www.ripe.net/see4 See you there! Kind regards, Gergana -- Gergana Petrova Conference Coordinator RIPE Network Coordination Centre Singel 258, 1016 AB Amsterdam, The Netherlands T: +31 20 535 4444 www.ripe.net

1 0

[news] RIPE Policy Proposals - January Update
by Marco Schmidt 21 Jan '15

21 Jan '15

Dear colleagues, This mail provides a simple overview of open policy proposals and the stage they have reached in the RIPE Policy Development Process (PDP). We will send one of these summary emails every month. By doing so, we hope to make the PDP more accessible to the community and help people keep track of what is being discussed. If you wish to join the discussions about a proposal, please do so on the relevant working group mailing list. If you have feedback on how we can improve these emails, please respond to me directly. Proposals Open for Discussion: 2014-03, “Remove Multihoming Requirement for AS Number Assignments” – Discussion open until 22 January 2015 2014-05, “Policy for Inter-RIR Transfers of Internet Resources” - Discussion open until 9 February 2015 2014-12, “Allow IPv6 Transfers” - Discussion open until 21 January 2015 2014-13, “Allow AS Number Transfers” - Discussion open until 21 January 2015 Proposals at Last Call: 2014-04, “Removing IPv6 Requirement for Receiving Space from the Final /8” – Opinion can be stated until 12 February 2015 2014-06, “Publication of Sponsoring LIR for Legacy Internet Resource Holders” – Opinion can be stated until 13 February 2015 Proposal Overviews: PROPOSAL: 2014-03, “Remove Multihoming Requirement for AS Number Assignments” OVERVIEW: This proposal aims to ease the requirements when requesting an Autonomous System (AS) Number. It is proposed to remove the need evaluation, limit the amount of AS Numbers per organization to 1,000 and require that 16-bit AS Numbers are multihomed after nine months. RIPE NCC IMPACT ANALYSIS: Includes point that it will be the End User that decides if the need for the AS Number is technically reasonable. STATUS: Review Phase WHERE TO COMMENT: The Address Policy Working Group – address-policy-wg(a)ripe.net DEADLINE: 22 January 2015 FULL PROPOSAL: http://www.ripe.net/ripe/policies/proposals/2014-03 PROPOSAL: 2014-05, “Policy for Inter-RIR Transfers of Internet Resources” OVERVIEW: This proposal aims to allow the global transfer of Internet resources. For transfers to the RIPE NCC service region from RIRs that require needs-based policies, recipients must provide the RIPE NCC with a plan for the use of at least 50% of the transferred resources within five years. RIPE NCC IMPACT ANALYSIS: Includes point that the RIRs ARIN (North America) and APNIC (Asia-Pacific) confirmed that the proposed text is compatible with their transfer policies. Currently, the proposed inter-RIR transfer policy would apply to IPv4 PA allocations, IPv4 PI assignments and legacy resources. STATUS: Review Phase WHERE TO COMMENT: The Address Policy Working Group – address-policy-wg(a)ripe.net DEADLINE: 9 February FULL PROPOSAL: http://www.ripe.net/ripe/policies/proposals/2014-05 PROPOSAL: 2014-12, “Allow IPv6 Transfers” OVERVIEW: The goal of this new proposal is to allow the transfer of IPv6 address space within the RIPE NCC service region. RIPE NCC IMPACT ANALYSIS: Includes point that the proposal would allow the transfer of IPv6 allocations and IPv6 Provider Independent (PI) assignments (or parts of them) from the rightfully registered resource holder to a new resource holder. STATUS:Review Phase WHERE TO COMMENT: The Address Policy Working Group – address-policy-wg(a)ripe.net DEADLINE: 21 January FULL PROPOSAL: http://www.ripe.net/ripe/policies/proposals/2014-12 PROPOSAL: 2014-13, “Allow AS Number Transfers” OVERVIEW: The goal of this new proposal is to allow the transfer of AS Numbers within the RIPE NCC service region. RIPE NCC IMPACT ANALYSIS: Includes point that the proposal would allow the transfer of AS Numbers from the rightfully registered resource holder to a new resource holder. STATUS: Review Phase WHERE TO COMMENT: The Address Policy Working Group – address-policy-wg(a)ripe.net DEADLINE: 21 January FULL PROPOSAL: http://www.ripe.net/ripe/policies/proposals/2014-13 ===== The following proposals are in Last Call. Rough consensus was declared and the purpose of this phase is to give the community a final opportunity to present well-justified objections in case anyone wants to oppose the proposal. PROPOSAL: 2014-04, “Removing IPv6 Requirement for Receiving Space from the Final /8” OVERVIEW: Currently, in order to receive a final /22 IPv4 allocation from the RIPE NCC, Local Internet Registries (LIRs) must have an IPv6 allocation in the RIPE NCC service region. This proposal aims to remove this requirement. STATUS: Last Call WHERE TO COMMENT: The Address Policy Working Group – address-policy-wg(a)ripe.net DEADLINE: 12 February FULL PROPOSAL: http://www.ripe.net/ripe/policies/proposals/2014-04 PROPOSAL: 2014-06, “Publication of Sponsoring LIR for Legacy Internet Resource Holders” OVERVIEW: This proposal aims to publish the link between legacy Internet resource holders and their sponsoring Local Internet Registry (LIR). STATUS: Last Call WHERE TO COMMENT: The RIPE NCC Services Working Group – ncc-services-wg(a)ripe.net DEADLINE: 13 February FULL PROPOSAL: http://www.ripe.net/ripe/policies/proposals/2014-06 The RIPE NCC provides an overview of current RIPE Policy Proposals on ripe.net: https://www.ripe.net/ripe/policies/current-proposals/current-policy-proposa… Full information about how the PDP works is available in ripe-614, “Policy Development Process in RIPE”: http://www.ripe.net/ripe/docs/ripe-614 We look forward to your involvement in the PDP. Kind regards, Marco Schmidt RIPE Policy Development Officer RIPE NCC

1 0

Internet Number Community IANA Proposal Published and Submitted
by Paul Rendek 16 Jan '15

16 Jan '15

Dear colleagues, On 15 January, the Consolidated RIR IANA Stewardship Proposal (CRISP) team submitted the Internet numbers community’s proposal on IANA stewardship to the IANA Stewardship Transition Coordination Team (ICG), as requested by the ICG. The proposal is available on the NRO website: https://www.nro.net/news/final-proposal-crisp This submission represents the culmination of discussions in each of the five Regional Internet Registry (RIR) communities, and around six weeks of intense work on the part of the CRISP team (made up of three representatives from each regional community) to consolidate the output from those discussions. This process involved publishing two earlier drafts and incorporating feedback received from the community to produce a final proposal that represents a consensus position of the global Internet numbers community. The key elements of the proposal are: - That the RIRs will establish a binding Service Level Agreement (SLA) with the IANA functions operator concerning provision of IANA services relating to the Internet number registries. - That ICANN will continue in its current role as IANA functions operator to ensure stability and continuity of IANA services, but with mechanisms in place for the Internet number community to change operator, should the need arise. - That a community-based Review Committee will be established to advise the RIRs on the performance of the IANA functions operator. - That all involved parties affirm that all relevant intellectual property rights (including trademarks, domain names and other rights) reside either in the public domain or, where appropriate, with the RIRs or another agreed entity. Over the coming months, the ICG will work to consolidate proposals received from the three affected communities (numbers, names and protocol parameters), with the goal of producing a single proposal on IANA stewardship for the National Telecommunications and Information Administration (NTIA) by the June 2015. Feedback from the global community will be an important element of this process, and regular updates will be posted to the RIPE Cooperation Working Group mailing list. More information on the IANA stewardship transition is available at: https://www.ripe.net/iana-stewardship-transition Best regards, Paul Rendek Director of External Relations RIPE NCC RIPE NCC CRISP Team representative

1 0

Call for Presentations RIPE 70
by Filiz Yilmaz 12 Jan '15

12 Jan '15

Dear colleagues, Please find the CFP for RIPE 70 below. The deadline for submissions is 1 March 2015. 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 70 will take place from 11-15 May 2015 in Amsterdam, The Netherlands. 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 70. 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://ripe70.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 1 March 2015, using the meeting submission system at https://ripe70.ripe.net/submit-topic/submission-form/. Proposals submitted after this date will be considered on a space-available basis. Important Dates regarding RIEP 70 can be found at: https://ripe70.ripe.net/programme/important-dates/ - Lightning talks should also be submitted using the meeting submission system (*https://ripe70.ripe.net/submit-topic/submission-form/ <https://ripe70.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://ripe70.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 panellists, presenters and moderators. - Due to potential technical issues, it is expected that most, if not all, presenters/panellists 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

Second Draft of Numbers Community IANA Stewardship Proposal Published
by Paul Rendek 08 Jan '15

08 Jan '15

Dear colleagues, The Consolidated RIR IANA Stewardship Proposal (CRISP) team has published a second draft of the Internet numbers community proposal on the transition of the IANA stewardship. A final call for community feedback has been issued, with the CRISP team planning to submit the finalised proposal to the IANA Stewardship Transition Coordination Group (ICG) on Thursday, 15 January. The second draft of the proposal is available at: http://www.nro.net/crisp-proposal-second-draft There is also a “redline version” that shows all changes made since the first draft: http:/www.nro.net/crisp-proposal-second-draft-change-control The deadline for providing feedback is Monday, 12 January 2015. The CRISP team strongly encourages community members in favour of this proposal to express their support, either via the RIPE Cooperation Working Group mailing list or via the ianaxfer(a)nro.net mailing list, as demonstrated community support may be important later in the IANA stewardship transition process. Some of the key points to note in this second draft: - Additional description on contract details, review committee and intellectual property rights - Description revised on Section V. NITA Requirements and Section VI. Community Process for more clarity - No changes to key elements of the proposal The CRISP team timeline for the coming weeks is as follows: Second draft to be published: 8 Jan 2015 Second draft comments close: 12 Jan 2015 Final proposal to be sent to ICG: 15 Jan 2015 More background on the IANA stewardship transition process is available at: https://www.ripe.net/iana-oversight-transition Details on the CRISP team, including members, timelines and working methods, are available at: https://nro.net/crisp-team Best regards, Paul Rendek Director of External Relations RIPE NCC

1 0

Last Day to Comment on IANA Stewardship Draft
by Chris Buckridge 05 Jan '15

05 Jan '15

Dear colleagues, A reminder that today is the last day for commenting on the first draft of the Internet numbers community’s IANA stewardship proposal. The draft, produced by the Consolidated RIR IANA Stewardship Proposal (CRISP) team, is available at: https://www.nro.net/wp-content/uploads/CRISP-IANA-PROPOSAL-First-Draft1.pdf After the comment period closes, the CRISP team will prepare a second public draft, based on the feedback received. The timeline for the remaining CRISP team work is: Second draft to be published: 8 Jan 2015 Final proposal to be sent to IANA Stewardship Transition Coordination Group (ICG): 15 Jan 2015 The CRISP team will hold its eighth teleconference today, 5 January, at 13:00 UTC. Details on how to join the call as an observer are included at the end of this email. More background on the IANA stewardship transition process is available at: https://www.ripe.net/iana-oversight-transition Details on the CRISP team, including members, timelines and working methods, are available at: https://nro.net/crisp-team Best regards, Chris Buckridge RIPE NCC ====== CRISP Team 8thTeleconference Monday, January 5, 2015 1:00pm | UTC | 2 hr Join WebEx meeting https://ripencc.webex.com/ripencc/j.php?MTID=mc7fe8904fb98d0e4132409b1f6362… Meeting number: 701 103 817 Meeting password: crispteam Join by phone 0800-051-3810 Call-in toll-free number (UK) +44-203-478-5289 Call-in toll number (UK) Accesscode: 701 103 817 Global call-in numbers: https://ripencc.webex.com/ripencc/globalcallin.php?serviceType=MC&ED=359012… Toll-free calling restrictions: http://www.webex.com/pdf/tollfree_restrictions.pdf

1 0

Last reminder - Call for ICANN Board Nominations
by Nick Hyrka 22 Dec '14

22 Dec '14

This message is sent on behalf of the Address Supporting Organization Address Council (ASO AC) ________________________________________________________________________ Last Reminder: Call for ICANN Board Nominations Close 31 December 2014 ________________________________________________________________________ This is a last reminder of the Address Supporting Organization Address Council (ASO AC) call for nominations for Seat Number 9 on the ICANN Board. Nominations period will close at 23:59 UTC on 31 December 2014. The ASO AC election procedures are found in Section 7 of the ASO Operating Procedures and are available on the ASO website at: https://aso.icann.org/documents/operational-documents/operating-procedures-… Article VI of the ICANN Bylaws states that: "At any given time, no two Directors selected by a Supporting Organization shall be citizens from the same country or of countries located in the same Geographic Region.” The ASO AC selection for Seat 10 of the ICANN Board of Directors resides in the APNIC region, so nominees for Seat 9 cannot reside in the APNIC region. Submit nominations by email to nominations2015(a)aso.icann.org including the following information: * Full name of the person being nominated * Contact email address for the person being nominated * Contact telephone number (if available) of the person being nominated * Full name of the person making the nomination * Contact email address for the person making the nomination * Contact telephone number of the person making the nomination All candidates must sign a Letter of Certification declaring that they are of good character. The selected candidate will undergo an independent due diligence review by an ICANN contractor, and announcement of the candidate will follow once this review has been successfully completed. The time frame for the selection process is as follows: - Nomination Phase 24 October 2014 to 31 December 2014 - Comment Phase 1 January 2015 to 31 March 2015 - Interview Phase 1 February 2015 to 31 March 2015 - Selection Process 1 April 2015 to 17 April 2015 - Due Diligence Review 18 April 2015 to 31 May 2015 - Announcement no later than 1 June 2015 All phases will conclude at 23:59 UTC on the date specified. For further information and ongoing notices about the selection process, please visit: https://aso.icann.org/aso-icann/icann-board-elections/2015-elections/ Regards, ASO Secretariat secretariat(a)aso.icann.org

1 0

IANA Stewardship: Give Feedback on the Draft Proposal From the RIR Communities
by Paul Rendek 19 Dec '14

19 Dec '14

Dear colleagues, The Consolidated RIR IANA Stewardship Proposal (CRISP) team has published the first draft of an Internet numbers community proposal for the future of the IANA stewardship. The draft is available here: https://www.nro.net/wp-content/uploads/CRISP-IANA-PROPOSAL-First-Draft1.pdf This document represents the first effort to bring together the outcomes of IANA stewardship discussions in the five RIR communities. It aligns closely with the principles agreed by the RIPE community: - It proposes a new contractual arrangement between the RIRs and ICANN for ICANN’s continuing management of the IANA functions - It does not seek to change any of the existing global or regional policy development structures - It provides for review of the IANA operator’s performance and compliance with contractual obligations The draft also proposes forming a community-based Review Committee that would produce an annual, non-binding report on the performance of the IANA operator. This concept evolved from the Multistakeholder Oversight Numbers Council (MONC) that was originally proposed by the LACNIC community. Community feedback is being sought on this draft proposal, with a deadline of Monday, 5 January 2015. Feedback can be sent to the global NRO IANA Transfer mailing list, <ianaxfer(a)nro.net>, or can be sent to the appropriate regional mailing lists. The RIPE CRISP representatives will be closely following discussions on the RIPE Cooperation Working Group mailing list, as well as the global discussion. Best regards, Paul Rendek Director of External Relations, RIPE NCC RIPE NCC CRISP team staff representative Important Links —— Subscribe to the RIPE Cooperation Working Group mailing list: http://www.ripe.net/mailman/listinfo/cooperation-wg/ Suscribe to the NRO IANA Transfer mailing list: https://www.nro.net/mailman/listinfo/ianaxfer Information on the CRISP team and its work [includes members, charter, teleconference minutes and audio]: https://www.nro.net/crisp-team Public archive of the internal CRISP mailing list: https://www.nro.net/pipermail/crisp/ RIR community timeline for IANA stewardship discussion and links to regional outputs: https://www.nro.net/nro-and-internet-governance/iana-oversight/timeline-for… RIPE NCC IANA stewardship information: https://www.ripe.net/iana-stewardship-transition

1 0