본문으로 건너뛰기

RIPE NCC · RIR 워치독

ASN assignment criteria revisited

안건별 기록은 여기서 확인하세요. 무엇이 바뀌었고, 왜 중요했는지, 누가 무엇을 주장했는지, 입장이 어떻게 변했는지, 무엇이 결정되었으며, 근거가 아직 부족한 부분은 어디인지 담고 있습니다.

출처 정보

Policy ID
2025-01
RIR
RIPE NCC
공식 지위
Withdrawn
도입됨
2025. 5. 6.
마지막 소스 업데이트
2026. 11. 18.

실제로 이 논쟁을 이끈 이는 누구일까?

10총 참여 주체
8토론 참여자
2정식 주체
32토론 메시지
5.8실질 참여자
84.4%상위 5개 토론 비중
350%를 커버하는 인물
580%를 커버하는 인물

정책 변화 과정

2.0
2025. 10. 16.
출처 정보 ↗

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.

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.

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.

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.

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.

논의 연표

  1. 공개 토론

    [address-policy-wg] DRAFT ASN assignment critera revisited

    32 토론 메시지 · 8 참여 주체

    출처 정보 ↗
  2. 도입됨

    도입됨

    출처 정보 ↗
  3. 공식 버전

    1.0

    출처 정보 ↗
  4. 공식 버전

    2.0

    출처 정보 ↗
  5. 공식 결정

    withdrawn

    withdrawn

    출처 정보 ↗

참여 주체

최종 업데이트:

불러오는 중…

출처 및 적용 범위

공개 토론 기록 보관소

커버리지

가장 처음 수집된 시점: 1992. 6. 30.
최근 수집: 2026. 11. 14.