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.
실제로 이 논쟁을 이끈 이는 누구일까?
정책 변화 과정
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.
출처 정보 −
If the name server set of a ccTLD, gTLD or a Tier 0/1 ENUM without anycasting technology applied would not pass the 'IANA Administrative Procedure for Root Zone Name Server Delegation and Glue Data' the TLD or the ENUM administrator출처 정보 ↗
출처 정보 +
Critical DNS infrastructure is defined as infrastructure providing Authoritative TLD or ENUM Tier 0/1 DNS lookup services. The organisation(s) applicable under this policy are TLDs operators as defined by IANA and ENUM operators as defined by the ITU.출처 정보 ↗
IPv4 anycast assignment limit · The proposed IPv4 entitlement increases from one dedicated /24 to up to four /24 prefixes per TLD or ENUM.
출처 정보 −
may receive a single dedicated /24 network prefix for the sole purpose of anycasting name servers, as described in RFC 3258.출처 정보 ↗
출처 정보 +
The organisation may receive up to four /24 prefixes per TLD/ENUM. These prefixes must be used for the sole purpose of anycasting authoratitve DNS servers for the stated TLD/ENUM, as described in RFC 3258.출처 정보 ↗
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.
출처 정보 −
The prefix will be assigned by the RIPE NCC directly to the TLD or ENUM operator, upon a request submitted via an existing LIR and will be registered with a status of 'ASSIGNED ANYCAST'출처 정보 ↗
출처 정보 +
Assignments for Critical DNS infrastructure are subject to Provider Independent (PI) number resource policies as described in this document and also to the policies described in the RIPE NCC document entitled "Contractual Requirements for Provider Independent Resources Holders in the RIPE NCC Service Region".출처 정보 ↗
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.
출처 정보 −
If the name server set of a ccTLD, gTLD or a Tier 0/1 ENUM without anycasting technology applied would not pass the 'IANA Administrative Procedure for Root Zone Name Server Delegation and Glue Data' the TLD or the ENUM administrator출처 정보 ↗
출처 정보 +
Critical DNS infrastructure is defined as infrastructure providing Authoratitve TLD or ENUM Tier 0/1 DNS lookup services. The organisation(s) applicable under this policy are TLDs operators as defined by IANA and ENUM operators as defined by the ITU.출처 정보 ↗
IPv6 anycast assignment limit · The proposed IPv6 entitlement increases from one dedicated /48 to up to four /48 prefixes per TLD or ENUM.
출처 정보 −
may receive a single dedicated /48 network prefix for the sole purpose of anycasting name servers, as described in RFC 3258.출처 정보 ↗
출처 정보 +
The organisation may receive up to four /48 prefixes per TLD/ENUM. These prefixes must be used for the sole purpose of anycasting authoratitve DNS servers for the stated TLD/ENUM, as described in RFC 3258.출처 정보 ↗
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.
출처 정보 −
The prefix will be assigned by the RIPE NCC directly to the TLD or ENUM operator, upon a request submitted via an existing LIR and will be registered with a status of 'ASSIGNED ANYCAST'출처 정보 ↗
출처 정보 +
The prefix will be assigned by the RIPE NCC directly to the organisation, upon a request properly submitted to the RIPE NCC, either directly or through a sponsoring LIR. Assignments for Critical DNS infrastructure are subject to the policies described in the RIPE NCC document entitled "Contractual Requirements for Provider Independent Resources Holders in the RIPE NCC Service Region".출처 정보 ↗
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.
출처 정보 −
Assignments for Critical DNS infrastructure are subject to Provider Independent (PI) number resource policies as described in this document and also to the policies described in the RIPE NCC document entitled "Contractual Requirements for Provider Independent Resources Holders in the RIPE NCC Service Region".출처 정보 ↗
출처 정보 +
Assignments for Critical DNS infrastructure are subject to the policies described in the RIPE document entitled "Contractual Requirements for Provider Independent Resource Holders in the RIPE NCC Service Region".출처 정보 ↗
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.
출처 정보 −
The prefix will be assigned by the RIPE NCC directly to the organisation, upon a request properly submitted to the RIPE NCC, either directly or through a sponsoring LIR.출처 정보 ↗
출처 정보 +
Assignments for Critical DNS infrastructure are subject to the policies described in the RIPE document entitled "Contractual Requirements for Provider Independent Resource Holders in the RIPE NCC Service Region".출처 정보 ↗
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.
출처 정보 −
Critical DNS infrastructure is defined as infrastructure providing Authoritative TLD or ENUM Tier 0/1 DNS lookup services. The organisations applicable under this policy are TLD operators as defined by IANA and ENUM operators as defined by the ITU.출처 정보 ↗
출처 정보 +
The organisations applicable under this policy are TLD managers, as recorded in the IANA's Root Zone Database and ENUM administrators, as 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.
출처 정보 −
These prefixes must be used for the sole purpose of anycasting authoritative DNS servers for the stated TLD/ENUM, as described in RFC 3258.출처 정보 ↗
출처 정보 +
These prefixes must be used for the sole purpose of anycasting authoritative DNS servers for the stated TLD/ENUM, as described in 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.
출처 정보 −
Critical DNS infrastructure is defined as infrastructure providing Authoritative TLD or ENUM Tier 0/1 DNS lookup services. The organisations applicable under this policy are TLD operators as defined by IANA and ENUM operators as defined by the ITU.출처 정보 ↗
출처 정보 +
The organisations applicable under this policy are TLD managers as, recorded in the IANA's Root Zone Database and ENUM administrators, as 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.
출처 정보 −
These prefixes must be used for the sole purpose of anycasting authoritative DNS servers for the stated TLD/ENUM, as described in RFC 3258.출처 정보 ↗
출처 정보 +
These prefixes must be used for the sole purpose of anycasting authoritative DNS servers for the stated TLD/ENUM, as described in BCP126/RFC4786출처 정보 ↗
논의 연표
공개 토론
Re: [address-policy-wg] 2005-02 Last Call for Comments (IP Assignments for Anycasting DNS)
1 토론 메시지 · 1 참여 주체
출처 정보 ↗공개 토론
[address-policy-wg] 2008-05 New Policy Proposal (Anycasting Tier 0/1 ENUM)
2 토론 메시지 · 2 참여 주체
출처 정보 ↗공개 토론
[address-policy-wg] 2008-05 Discussion Phase extended until 12 November 2008 (Anycasting Tier 0/1 ENUM)
1 토론 메시지 · 1 참여 주체
출처 정보 ↗공개 토론
[address-policy-wg] Anycasting Assignments for TLDs and Tier 0/1 ENUM Implemented
1 토론 메시지 · 1 참여 주체
출처 정보 ↗
참여 주체
불러오는 중…
출처 및 적용 범위
공개 토론 기록 보관소
- 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.
