RIPE NCC · RIR 워치독
ASN assignment criteria revisited
안건별 기록은 여기서 확인하세요. 무엇이 바뀌었고, 왜 중요했는지, 누가 무엇을 주장했는지, 입장이 어떻게 변했는지, 무엇이 결정되었으며, 근거가 아직 부족한 부분은 어디인지 담고 있습니다.
출처 정보
- Policy ID
- 2025-01
- RIR
- RIPE NCC
- 공식 지위
- Withdrawn
- 도입됨
- 2025. 5. 6.
- 마지막 소스 업데이트
- 2026. 11. 18.
실제로 이 논쟁을 이끈 이는 누구일까?
정책 변화 과정
General ASN requirements separated from additional-ASN requests · Version 2 places a unique external routing policy, a RIPE Database routing-policy entry and third-party peering under a general ASNs are required to heading, then separately lists what an additional-ASN applicant must provide. The first ASN remains available without application justification. That does not mean the revised operative text exempts the first ASN from every operational requirement, despite the broader wording retained in the rationale.
출처 정보 −
Requirements for additional ASNs are: A unique external routing policy for the Autonomous System must be provided. The uniqueness of the routing policy includes the announced prefixes. The Autonomous System must peer with a third party.출처 정보 ↗
출처 정보 +
Have a unique external routing policy. The uniqueness of the routing policy includes the announced prefixes. Have a routing policy defined in the RIPE Database. Peer with a third party.출처 정보 ↗
Routing-policy registration and off-GRT documentation · The old wording requests a routing policy for an ASN intended to appear in the global routing table and recommends RPSL. Version 2 instead requires a policy defined in the RIPE Database in the general ASN conditions and omits the explicit RPSL recommendation. Documentation of a non-visible purpose remains required for an ASN used outside the global routing table.
출처 정보 −
When requesting an AS Number to be visible in the Global Routing Table (GRT), the routing policy of the Autonomous System must be provided. The new unique routing policy should be defined in RPSL language, as used in the RIPE Database.출처 정보 ↗
출처 정보 +
Have a routing policy defined in the RIPE Database. Peer with a third party. In case the ASN is used for a purpose that is not visible in the GRT, documentation on the non-visible purpose (e.g., a reference to the assigned IXP LAN prefixes) must be provided.출처 정보 ↗
Six-month use expectation and intermittent use · Version 2 replaces the mandatory fulfilment of approved application criteria within six months with a should-be-in-use expectation over the same period. It describes intermittent research, measurement and event uses as subject to RIPE NCC discretion and still requires a benefit statement. The interval is unchanged, while the wording and the explicit discretion differ.
출처 정보 −
Reasonable periodic use cases may be allowed. A benefit statement for such must be provided. The requester must fulfil the criteria for which the application was approved within six months after the ASN is issued.출처 정보 ↗
출처 정보 +
ASNs should be in use within six months after the ASN is issued. Intermittent usage such as research, measurements, events, etc. may be allowed at the discretion of the RIPE NCC. A benefit statement for such usage must be provided.출처 정보 ↗
Justification for leaving existing ASNs inactive · Version 2 explicitly requires an additional-ASN requester to explain why inactive existing ASNs cannot be used. Approval may still depend on compliance by existing ASNs, now expressly at RIPE NCC discretion; the old separate reference to up-to-date documentation in that approval sentence is removed.
출처 정보 −
Approval of an additional ASN may depend on the fulfilment of criteria and up-to-date documentation for existing ASNs.출처 정보 ↗
출처 정보 +
A reason for why inactive existing ASNs cannot be used. Approval of an additional ASN may depend on the fulfilment of ASN requirements for existing ASNs, at the discretion of the RIPE NCC.출처 정보 ↗
Detailed verification procedure omitted · Version 2 omits the old instructions to verify visible ASNs through the global routing table, request operational proof for off-table ASNs, and treat insufficient proof as failure. It retains discretion over approval based on existing ASN requirements. The omission changes the prescribed verification detail; it does not establish that RIPE NCC can no longer check compliance.
출처 정보 −
In case of an ASN visible in the GRT, RIPE NCC verifies that the ASN fulfils the criteria by checking the GRT. In case of an off-GRT ASN, RIPE NCC may request operational proof that the criteria are fulfilled. Failing to provide sufficient proof is considered as not fulfilling the criteria.출처 정보 ↗
출처 정보 +
Approval of an additional ASN may depend on the fulfilment of ASN requirements for existing ASNs, at the discretion of the RIPE NCC.출처 정보 ↗
논의 연표
참여 주체
불러오는 중…
출처 및 적용 범위
공개 토론 기록 보관소
- ripencc-address-policy-wg –
- ripencc-accountability-tf-ripe.net –
- ripencc-agm-nominations-ripe.net –
- ripencc-all-anchors-ripe.net –
- ripencc-anti-abuse-wg-ripe.net –
- ripencc-atlas-sponsors-ripe.net –
- ripencc-atlas-sw-probes-ripe.net –
- ripencc-bcop-ripe.net –
- ripencc-coc-tf-ripe.net –
- ripencc-connect-bof-ripe.net –
- ripencc-connect-wg-ripe.net –
- ripencc-cooperation-wg-ripe.net –
- ripencc-db-help-ripe.net –
- ripencc-db-wg-ripe.net –
- ripencc-diversity-ripe.net –
- ripencc-dns-resolver-tf-ripe.net –
- ripencc-dns-wg-ripe.net –
- ripencc-dp-tf-ripe.net –
- ripencc-eb-candidates-ripe.net –
- ripencc-eix-wg-ripe.net –
- ripencc-election-cc-team-ripe.net –
- ripencc-enum-announce-ripe.net –
- ripencc-enum-wg-ripe.net –
- ripencc-hackathon-list-ripe.net –
- ripencc-icann-plan-ripe.net –
- ripencc-iot-wg-ripe.net –
- ripencc-ipmap-ripe.net –
- ripencc-ipmt-dev-ripe.net –
- ripencc-ipv6-wg-ripe.net –
- ripencc-irrtoolset-ripe.net –
- ripencc-lir-wg-ripe.net –
- ripencc-mat-wg-ripe.net –
- ripencc-measure-voip-ripe.net –
- ripencc-members-discuss-unmoderated-ripe.net –
- ripencc-members-discuss-ripe.net –
- ripencc-myasntesting-ripe.net –
- ripencc-ncc-announce-ripe.net –
- ripencc-ncc-services-wg-ripe.net –
- ripencc-opensource-wg-ripe.net –
- ripencc-persian-lir-ripe.net –
- ripencc-policy-announce-ripe.net –
- ripencc-raci-list-ripe.net –
- ripencc-regional-russia-ripe.net –
- ripencc-regional-ukraine-ripe.net –
- ripencc-ripe-atlas-ambassadors-ripe.net –
- ripencc-ripe-atlas-tools-maintainers-ripe.net –
- ripencc-ripe-atlas-ripe.net –
- ripencc-ripe-chair-discuss-ripe.net –
- ripencc-ripe-db-requirements-tf-ripe.net –
- ripencc-ripe-forum-test-ripe.net –
- ripencc-ripe-list-unmoderated-ripe.net –
- ripencc-ripe-list-ripe.net –
- ripencc-ripe-parents-ripe.net –
- ripencc-ripecast-ripe.net –
- ripencc-rirs-lea-ripe.net –
- ripencc-ris-int-ripe.net –
- ripencc-ris-users-ripe.net –
- ripencc-routing-wg-ripe.net –
- ripencc-rpslng-ripe.net –
- ripencc-security-wg-ripe.net –
- ripencc-see-regional-ripe.net –
- ripencc-techsec-wg-ripe.net –
- ripencc-tld-wg-ripe.net –
- ripencc-tt-tf-ripe.net –
- www.ripe.net/community/wg/active-wg/ap/minutes
- ripencc-green-tech-hackathon-orga-ripe.net
- ripencc-nccdays-pc-ripe.net
커버리지
가장 처음 수집된 시점: 1992. 6. 30.
최근 수집: 2026. 11. 14.
