RBI advises NBFCs to migrate to IPv6 preferably by December 2012
Current · Source: Reserve Bank of India · RBI/2012-13/289 · issued 08 Nov 2012 · ~1 min read
Quick answerRBI has advised all NBFCs to complete migration from IPv4 to IPv6 preferably by December 2012, aligning with the National Telecom Policy 2012. Form a special team to manage the transition.
The rule, in the simplest words
All NBFCs (companies that lend money but are not banks) must switch from IPv4 (old internet address system) to IPv6 (new internet address system), preferably by December 2012.
Create a special team to plan and carry out the IPv6 migration.
Make sure every website, payment gateway (online money‑transfer system), and other online tools work with IPv6.
If you need help, call Shri R. M. Agarwal at the Department of Telecommunication for technical assistance.
How it plays out — a real example
Rohit, a gold‑loan officer in Indore, notices the NBFC’s online loan portal still uses IPv4. He forms a small team, reaches out to Shri R. M. Agarwal for guidance, and by November they upgrade the portal and the payment gateway to IPv6, so customers can apply for loans and pay online without any hiccups.
What changed
RBI issued a circular on November 8, 2012, advising NBFCs to migrate from IPv4 to IPv6. The government prefers completion by December 2012, as IPv4 addresses are nearly exhausted. This follows the National Telecom Policy 2012's goal of broadband on demand by 2015.
What it means for you
NBFCs must upgrade their internet infrastructure to IPv6 to support future broadband growth and avoid service disruptions. Failure to migrate could affect online services, payment gateways, and customer access. Proactive planning is essential to meet the deadline.
What you must do
Form a dedicated team to oversee IPv6 migration.
Ensure all websites, payment gateways, and online systems are IPv6-compatible preferably by December 2012.
Contact Shri R. M. Agarwal at DoT (9868133440) for technical assistance if needed.
Who it affects
All Non-Banking Financial Companies (NBFCs), Residuary Non-Banking Companies (RNBCs), IT and operations teams within these entities
❓ Common questions
Why is IPv6 migration necessary for NBFCs?
IPv4 addresses are nearly exhausted, and the National Telecom Policy 2012 aims for broadband on demand by 2015. IPv6 ensures continued internet growth and service availability.
What is the deadline for migration?
The government prefers completion by December 2012, as stated in the RBI circular.
Who can help with IPv6 implementation?
Shri R. M. Agarwal, DDG (NT) at DoT, is leading the support team and can be reached at 9868133440.
📜 Read the original circular — full text as issued by RBI
RBI/2012-13/289
DNBS(Inf.).CC. No 309/24.01.022/2012-13
November 08, 2012
All Non Banking Financial Companies /
Residuary Non Banking Companies
Dear Sir/Madam,
Readiness of major service providers to migrate from IPv4 to IPv6
As you may be aware, the Government has envisaged providing “Broadband on Demand” by 2015 in the recently unveiled National Telecom Policy (NTP) – 2012 emphasizing the role of Internet as catalyst for socio-economic development of a country and serves as an effective medium of various citizen centric services in today’s information economy. Since the current version of Internet Protocol (IPv4) has almost run out of addresses, the broadband revolution is sure to ride on next generation Internet Protocol (IPv6). The NTP-2012 recognizes the futuristic role of IPv6 and aims to achieve substantial transition to IPv6 in the country.
Department of Telecommunication under the Ministry of Communication and Information Technology, Government of India has undertaken the initiative of migration from IPv4 to IPv6.
Since migration to IPv6 is an eventuality that has to be accepted and manage proactively, government wants it to be done in a planned way rather than against time. They have expressed that the migration of all payment gateways, banks, financial institutions, insurance companies etc. including their web sites should be completed preferable by December 2012. You may initiate necessary action by constituting a special team to complete the migration within the stipulated time.
In case you need any clarifications/assistance on IPv6 implementation, kindly contact Shri R. M. Agarwal, DDG (NT), DoT (Mobile number 9868133440) who is heading the team which is providing relevant support to all stakeholders.
Yours faithfully,
(Uma Subramaniam)
Chief General Manager-in-charge
Reproduced for reference with acknowledgment — Source: Reserve Bank of India · RBI/2012-13/289 · issued 08 Nov 2012. The plain-English explanation above is BankPulse’s own independent summary.
Ensure all websites, payment gateways, and online systems are IPv6-compatible preferably by December 2012.
📜 Compliance
Form a dedicated team to oversee IPv6 migration.
Contact Shri R. M. Agarwal at DoT (9868133440) for technical assistance if needed.
Grouped from the action items above — a single circular may involve more than one team.
Worked example & action-note template
Example: if you are a Compliance officer at a bank this circular applies to (All Non-Banking Financial Companies (NBFCs), Residuary Non-Banking Companies (RNBCs), IT and operations teams within these entities), your first concrete step on “RBI advises NBFCs to migrate to IPv6 preferably by December 2012” is: “Form a dedicated team to oversee IPv6 migration.” (RBI issued this 08 Nov 2012).
Circular: RBI/2012-13/289 -- RBI advises NBFCs to migrate to IPv6 preferably by December 2012
Issued: 08 Nov 2012
Action required: Form a dedicated team to oversee IPv6 migration.
Action required: Ensure all websites, payment gateways, and online systems are IPv6-compatible preferably by December 2012.
Action required: Contact Shri R. M. Agarwal at DoT (9868133440) for technical assistance if needed.
Owner: ____________ Target date: ____________
Board/committee approval needed? Y / N
Evidence filed in compliance register on: ____________
Built only from this circular’s own published fields — not legal advice; always confirm against the official RBI source.
💬 Banker Discussion
Discuss this circular with fellow bankers — reply, upvote what helps, report what doesn’t belong. Be professional; no client data. Views are the commenter’s own, not BankPulse’s.
BankPulse Compliance Evidence Pack — generated 03 Aug 2026 · status cross-checked against RBI’s official withdrawal register (refreshed weekly). Official RBI source: https://www.rbi.org.in/Scripts/NotificationUser.aspx?Id=7684&Mode=0 — Plain-English summary by BankPulse (bankpulse.ai), reviewed by our expert reviewer, CA Amit Jain. Independent platform, not affiliated with the Reserve Bank of India; is our own plain-English paraphrase, not RBI’s original wording.
Help us keep this accurate
Found an inaccuracy or have an improvement? Tell us. Every report is reviewed by our team before any change is made — nothing goes live unverified.
Public beta — plain-English informational summaries. Always verify against the official RBI source (circular number cited on every page) before making compliance, credit, treasury, audit, or operational decisions. · Join our WhatsApp channel ↗
BANKPULSE · FREE DAILY BRIEF
Get RBI updates for your role
Every important RBI update, decoded in plain English — for your career, exams & financial awareness.
We collect only your email, name and role, used solely to send your brief — never sold or shared. Withdraw anytime via the unsubscribe link in any email. Independent platform, not affiliated with the RBI. Information, not legal advice.
REPORT AN ERROR · BETA
Spotted an error? Earn 500 BankPulse Credits
Help us stay accurate. If your correction is verified true and approved by our founder, you earn 500 BankPulse Credits — redeemable when the platform monetises.
Reviewed by a human before any credit is awarded. We never change the site from crowd input without verification.
WANT A NEW FEATURE · BETA
What would make BankPulse more useful for you?
Tell us what to build next — a tool, a data view, a role page, anything. We read every suggestion.
Thank you — your ideas directly shape what we build.