4 Byte AS Number Update Geoff Huston August 2008.

Slides:



Advertisements
Similar presentations
32-bit AS Numbers The view from the 16-bit ASN BGP world
Advertisements

RPKI Standards Activity Geoff Huston APNIC February 2010.
AS Numbers - Again Geoff Huston APNIC August 2009
BGP AS Number Exhaustion Geoff Huston Research activity supported by APNIC March 2003.
4-Byte AS number registry Policy Proposal [LACNIC Proposal ] Geoff Huston APNIC 25 May.
End of the Internet Predicted! Torrent at 11. The Oracle Bones of IPv4 Some personal divination by Geoff Huston APNIC.
4-Byte AS Numbers The view from the old BGP world Geoff Huston October 2006 APNIC.
IPv4 Unallocated Address Space Exhaustion Geoff Huston Chief Scientist APNIC APNIC 24, September 2007.
IPv6 Transition for Enterprises Light Reading Live 14 July 2011 John Curran President and CEO ARIN.
Deploying IPv6: The time is now Are you ready? SFTA 24 May 2012 John Curran President and CEO, ARIN.
Disruption (and Recovery) of the ISP Business Model with IPv4 Depletion PTC12 15 January 2012 John Curran President and CEO, ARIN.
IPv6 Deployment CANTO Nate Davis, Chief Operating Officer 13 August 2014.
IPv6: Paving the way for next generation networks Tuesday, 16 July 2013 Nate Davis Chief Operating Officer, ARIN.
Marla Azinger, Frontier Communications
1 Muhammed Rudman
IPv4 Depletion IPv6 Adoption 3 February /8s Remaining.
1 Overview of policy proposals Policy SIG Wednesday 26 August 2009 Beijing, China.
Dynamic Routing Scalable Infrastructure Workshop, AfNOG2008.
IPv4 Depletion and IPv6 Adoption Today Community Use Slide Deck Courtesy of ARIN May 2014.
An Operational Perspective on BGP Security Geoff Huston GROW WG IETF 63 August 2005.
© 2009 Cisco Systems, Inc. All rights reserved. ROUTE v1.0—6-1 Connecting an Enterprise Network to an ISP Network Considering the Advantages of Using BGP.
Allocations vs Announcements A comparison of RIR IPv4 Allocation Records with Global Routing Announcements Geoff Huston May 2004 (Activity supported by.
Performance-based BGP Routing Mechanism draft-xu-idr-performance-routing-00 Xiaohu Xu (Huawei) Hui Ni (Huawei) Mohamed Boucadair (France.
IPv4 Address Lifetime Expectancy Geoff Huston Research activity supported by APNIC The Regional Internet Registries s do not make forecasts or predictions.
Expanding the Internet: The IPv4 to IPv6 transition Global Mobile Internet & IPv6 Next Generation Internet Summit 2009 Paul Wilson Director General, APNIC.
1 IPv6 Address Space Management Report of IPv6 Registry Simulation Policy SIG 1 Sept 2004 APNIC18, Nadi, Fiji Geoff Huston.
IPv4 Address Lifetime Presented by Nurani Nimpuno, APNIC Research activity conducted by Geoff Huston and supported by APNIC.
An overview of IP addressing history and policy issues Leo Vegoda Number Resources Manager, IANA.
Lecture 4: BGP Presentations Lab information H/W update.
APNIC Depletion of the IPv4 free address pool – IPv6 deployment The day after!! 8 August 2008 Queenstown, New Zealand In conjunction with APAN Cecil Goldstein,
1 TWNIC Update Sheng Wei Kuo, TWNIC NIR SIG, 28 th APNIC OPM.
IPv4 Unallocated Address Space Exhaustion Geoff Huston Chief Scientist APNIC November 2007.
Policy Experience Report Leslie Nobile. Review existing policies – Ambiguous text/Inconsistencies/Gaps/Effectiveness Identify areas where new or modified.
New World BGP Geoff Huston January2010 APNIC. 16-bit AS Number Map.
Policy Implementation & Experience Report Leslie Nobile.
1 AS Consumption Patterns Geoff Huston APNIC May 2005.
Prop-065-v001 Format for delegation and recording of 4-byte AS numbers APNIC26 - Christchurch NZ.
1 IPv4 Address Lifetime Presented by Paul Wilson, APNIC Research activity conducted by Geoff Huston and supported by APNIC.
AS Numbers NANOG 35 Geoff Huston APNIC. Current AS Number Status.
IPv4 Address Lifetime SANOG IV Presented by Nurani Nimpuno, APNIC Research activity conducted by Geoff Huston and supported by APNIC.
Tracking the Internet’s BGP Table Geoff Huston Telstra December 2000.
APNIC Update The state of IP address distribution and its impact to business operations Elly Tawhai Senior Internet Resource Analyst/Liaison Officer, Pacific,
1 Transition to IPv6: Should ISPs consider it now? PITA 11th AGM Meeting 2007 Tahiti, French Polynesia 24 April 2007.
Policy SIG Report APNIC AGM Friday 29 August 2008 Christchurch, New Zealand 1.
1 IPv6 Allocation and Policy Update Global IPv6 Summit in China 2007 April 12, 2007 Guangliang Pan.
RIPE Network Coordination Centre October Andrew de la Haye 32-bit ASN Adjustment to Global Policy Proposal Stacy Hughes Andrew.
IPv6 Adoption Status and Scheduling for Sustainable Development 24 July 2012 Nate Davis Chief Operating Officer, ARIN.
AS Numbers - Again Geoff Huston APNIC October 2009
Boarder Gateway Protocol (BGP)
Non optimal routing caused by incompatibility of 32-bit ASN with the old router software. KazRENA case study.
Non optimal routing caused by incompatibility of 32-bit ASN with the old router software. KazRENA case study.
Addressing 2016 Geoff Huston APNIC.
René Wilhelm & Henk Uijterwaal RIPE NCC APNIC21, 18 September 2018
IP Addresses in 2016 Geoff Huston APNIC.
Geoff Huston APNIC August 2009
The IPv4 Consumption Model
IPv6 Address Space Management Report of IPv6 Registry Simulation
Geoff Huston September 2002
An Update on Multihoming in IPv6 Report on IETF Activity
An Update on BGP Support for 4-byte ASN
IPv6 Address Space Management Report of IPv6 Registry Simulation
RIPE October 2005 Geoff Huston APNIC
IPv6 Policy and Allocation Update
Nurani Nimpuno On behalf of Geoff Huston APNIC 25 May 2006
End of the Internet Predicted!
4-Byte AS number registry Policy Proposal [LACNIC Proposal ]
Overview of policy proposals
IPv4 Address Lifetime Expectancy
Design Expectations vs. Deployment Reality in Protocol Development
4-Byte AS Numbers The view from the old BGP world
Presentation transcript:

4 Byte AS Number Update Geoff Huston August 2008

The story so far … 16 bit AS number field defined by BGP Used in BGP for –peer identification –path metric calculation –loop detection

16-bit AS Number Pool Status

16-bit AS Number Consumption

Crunch Time 24 April

The IETF had a plan … Adjust BGP to use 32-bit AS numbers

The IETF had a plan … Adjust BGP to use 32-bit AS numbers Make the adjustment backward compatible: –use AS as a “token holder” for backward compatibility –no existing BGP deployments need to change at all - the Internet will Just Work throughout the transition –Use “new” BGP for new routing domains that use these extended length 32-bit AS numbers

The IETF had a plan … Adjust BGP to use 32-bit AS numbers Make the adjustment backward compatible: –use AS as a “token holder” for backward compatibility –no existing BGP deployments need to change at all - the Internet will Just Work throughout this transition –Use “new” BGP for new routing domains that use these extended length 32-bit AS numbers IANA to open up a 32-bit AS number registry

The IETF had a plan … Adjust BGP to use 32-bit AS numbers Make the adjustment backward compatible: –use AS as a “token holder” for backward compatibility –no existing BGP deployments need to change at all - the Internet will Just Work throughout this transition –Use “new” BGP for new routing domains that use these extended length 32-bit AS numbers IANA to open up a 32-bit AS number registry Published as a Proposed Internet Standard: RFC 4893

−The RIRs had a policy … Start allocating 32-bit only AS numbers as of 1 January 2007 –but only upon request –and you get a 16 bit AS number otherwise

The RIRs had a policy … Start allocating 32-bit only AS numbers as of 1 January 2007 –but only upon request –and you get a 16 bit AS number otherwise Flip the bits on 1 January 2009 –16 bit AS numbers still available if you ask for them –otherwise you get a 32-bit only AS number

The RIRs had a policy … Start allocating 32-bit only AS numbers as of 1 January 2007 –but only upon request –and you get a 16 bit AS number otherwise Flip the bits on 1 January 2009 –16 bit AS numbers still available if you ask for them –otherwise you get a 32-bit only AS number Drop the distinction on 1 January 2010 –They are all just one big pool of AS numbers once more

Policy Objectives Provide vendors, suppliers, ISPs and others ample time to implement 32-bit support in BGP and related operational support systems that manipulate AS numbers

Policy Objectives Provide vendors, suppliers, ISPs and others ample time to implement 32-bit support in BGP and related operational support systems that manipulate AS numbers Set forth clear dates in terms of milestones in the transition to 32-bit AS numbers

Policy Objectives Provide vendors, suppliers, ISPs and others ample time to implement 32-bit support in BGP and related operational support systems that manipulate AS numbers Set forth clear dates in terms of milestones in the transition to 32-bit AS numbers Encourage advance planning and avoid disruptive exhaustion of the 16-bit AS number pool prior to general availability of 32-bit AS support in BGP and related systems

How are we doing? August 2008 AS statistics 88 Allocated 32-bit only AS numbers (Total of 43,670 allocated AS numbers) 12 Advertised 32-bit only AS numbers (Total of 28,909 advertised AS numbers)

No general 32-bit BGP adoption yet Vendor situation is still lagging for 32 bit AS number support in BGP –My current understanding of vendor support: Cisco: IOS-XR 3.4 Juniper: JUNOSe Redback others: ? –Open Source BGP: Quagga OpenBGPd

Some Timely Questions Are your operational support systems capable of supporting 32-bit AS numbers? –Can you support customers / peers / upstreams peering with you when they use 32- bit AS numbers? –Can you cope with multiple AS BGP peers?

Some Timely Questions Are your operational support systems capable of supporting 32-bit AS numbers? –Can you support customers / peers / upstreams peering with you when they use 32-bit AS numbers? –Can you cope with multiple AS23456 BGP peers? If you intend to use BGP for a new domain does your router vendor support 32-bit AS number support in BGP?

For more information …

For more information …

Thank You Questions?