본문으로 건너뛰기

RIPE NCC · RIR 워치독

Anycasting Assignments for TLDs and Tier 0/1 ENUM

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

출처 정보

Policy ID
2008-05
RIR
RIPE NCC
공식 지위
Accepted
도입됨
2022. 2. 14.
마지막 소스 업데이트
2026. 11. 11.

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

16총 참여 주체
14토론 참여자
2정식 주체
18토론 메시지
10.1실질 참여자
50%상위 5개 토론 비중
550%를 커버하는 인물
1180%를 커버하는 인물

정책 변화 과정

2.0
승인됨 · Accepted
2009. 4. 27.
출처 정보 ↗

IPv4 anycast eligibility · Eligibility is changed from a test based on whether a ccTLD, gTLD or Tier 0/1 ENUM name-server set would fail the cited IANA procedure to a category-based rule covering TLD operators defined by IANA and ENUM operators defined by the ITU as critical DNS infrastructure.

IPv4 anycast assignment limit · The proposed IPv4 entitlement increases from one dedicated /24 to up to four /24 prefixes per TLD or ENUM.

IPv4 assignment conditions · The proposed IPv4 text removes the explicit direct-assignment-through-an-existing-LIR procedure and instead makes critical-DNS assignments subject to the general Provider Independent number-resource policies and the stated contractual requirements.

IPv6 anycast eligibility · Eligibility is changed from a test based on whether a ccTLD, gTLD or Tier 0/1 ENUM name-server set would fail the cited IANA procedure to a category-based rule covering TLD operators defined by IANA and ENUM operators defined by the ITU as critical DNS infrastructure.

IPv6 anycast assignment limit · The proposed IPv6 entitlement increases from one dedicated /48 to up to four /48 prefixes per TLD or ENUM.

IPv6 assignment procedure and contractual conditions · The request path is broadened from submission through an existing LIR to submission either directly to the RIPE NCC or through a sponsoring LIR, and the revised text adds the stated contractual requirements for critical-DNS assignments.

3.0
승인됨 · Accepted
2009. 4. 27.
출처 정보 ↗

Existing IPv4 policy baseline · The document refreshes the quoted existing IPv4 rule from RIPE-424 to ripe-449. The newer baseline replaces the explicit direct-assignment-via-existing-LIR wording with applicability of Provider Independent number-resource policies and the contractual requirements. This is a change to the comparison baseline, not the proposal's new entitlement.

Proposed IPv4 policy dependencies · The proposed IPv4 text drops the explicit statement that critical-DNS assignments are subject to the general Provider Independent number-resource policies, while retaining the contractual-requirements reference.

Existing IPv6 policy baseline · The quoted existing IPv6 rule is refreshed from RIPE-421 to ripe-466: the baseline now names only the TLD administrator, allows a request either directly or through a sponsoring LIR, and adds the contractual-requirements condition. This is a baseline update rather than a new proposal entitlement.

Proposed IPv6 assignment procedure · The revised proposed IPv6 text removes the sentence explicitly assigning the prefix directly to the organisation and allowing requests either directly or through a sponsoring LIR; it proceeds instead from the anycast-use rule to the contractual-requirements condition.

4.0
승인됨 · Accepted
2009. 4. 27.
출처 정보 ↗

IPv4 eligible operator definition · The IPv4 text replaces the generic critical-DNS definition and TLD/ENUM operators defined by IANA or ITU with TLD managers recorded in IANA's Root Zone Database and ENUM administrators assigned by the ITU.

IPv4 assignment-cap wording · The cap is made explicit as up to four /24 prefixes per TLD and up to four /24 prefixes per ENUM, replacing the shorter 'per TLD/ENUM' formulation.

IPv4 anycast technical standard · The cited technical basis for use of the prefixes changes from RFC 3258 to BCP126/RFC4786.

IPv6 eligible operator definition · The IPv6 text replaces the generic critical-DNS definition and TLD/ENUM operators defined by IANA or ITU with TLD managers recorded in IANA's Root Zone Database and ENUM administrators assigned by the ITU.

IPv6 assignment-cap wording · The cap is made explicit as up to four /48 prefixes per TLD and up to four /48 prefixes per ENUM, replacing the shorter 'per TLD/ENUM' formulation.

IPv6 anycast technical standard · The cited technical basis for use of the prefixes changes from RFC 3258 to BCP126/RFC4786.

논의 연표

  1. 공개 토론

    Re: [address-policy-wg] 2005-02 Last Call for Comments (IP Assignments for Anycasting DNS)

    1 토론 메시지 · 1 참여 주체

    출처 정보 ↗
  2. 공개 토론

    Re: [address-policy-wg] PI for Not-DNS Anycast.

    1 토론 메시지 · 1 참여 주체

    출처 정보 ↗
  3. 공개 토론

    [address-policy-wg] 2008-05 New Policy Proposal (Anycasting Tier 0/1 ENUM)

    2 토론 메시지 · 2 참여 주체

    출처 정보 ↗
  4. 공개 토론

    [address-policy-wg] comments on 2008-05 Anycasting Tier 0/1 ENUM

    1 토론 메시지 · 1 참여 주체

    출처 정보 ↗
  5. 공개 토론

    [address-policy-wg] 2008-05 Discussion Phase extended until 12 November 2008 (Anycasting Tier 0/1 ENUM)

    1 토론 메시지 · 1 참여 주체

    출처 정보 ↗
  6. 공개 토론

    [address-policy-wg] DRAFT agenda for RIPE address policy WG in Dubai

    2 토론 메시지 · 2 참여 주체

    출처 정보 ↗
  7. 공개 토론

    Re: [address-policy-wg] Re: Assignments for Critical Infrastruction

    3 토론 메시지 · 3 참여 주체

    출처 정보 ↗
  8. 공개 토론

    [address-policy-wg] Assignments for Critical Infrastruction

    1 토론 메시지 · 1 참여 주체

    출처 정보 ↗
  9. 공개 토론

    Re: [address-policy-wg] IPv6 assignment for the RIPE meeting network

    3 토론 메시지 · 3 참여 주체

    출처 정보 ↗
  10. 공개 토론

    [address-policy-wg] (Draft) Agenda for RIPE 58

    1 토론 메시지 · 1 참여 주체

    출처 정보 ↗
  11. 공식 버전

    1.0

    승인됨 · Accepted

    출처 정보 ↗
  12. 공식 버전

    2.0

    승인됨 · Accepted

    출처 정보 ↗
  13. 공식 버전

    3.0

    승인됨 · Accepted

    출처 정보 ↗
  14. 공식 버전

    4.0

    승인됨 · Accepted

    출처 정보 ↗
  15. 공식 결정

    accepted

    accepted

    출처 정보 ↗
  16. 공개 토론

    [address-policy-wg] Anycasting Assignments for TLDs and Tier 0/1 ENUM Implemented

    1 토론 메시지 · 1 참여 주체

    출처 정보 ↗
  17. 공개 토론

    [address-policy-wg] agenda for upcoming APWG meeting

    1 토론 메시지 · 1 참여 주체

    출처 정보 ↗
  18. 도입됨

    도입됨

    출처 정보 ↗

참여 주체

최종 업데이트:

불러오는 중…

출처 및 적용 범위

공개 토론 기록 보관소

커버리지

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