본문으로 건너뛰기

RIPE NCC · RIR 워치독

Validation of "abuse-mailbox"

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

출처 정보

Policy ID
2019-04
RIR
RIPE NCC
공식 지위
Withdrawn
도입됨
2019. 5. 15.
마지막 소스 업데이트
2026. 11. 11.

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

1총 참여 주체
1정식 주체

정책 변화 과정

2.0
철회됨 · Withdrawn
2020. 4. 15.
출처 정보 ↗

Receipt of abuse reports · Version 2.0 replaces the detailed mailbox-handling passage with three requirements: recipient intervention, no mandatory reporting form, and guaranteed receipt of reports and supporting logs, examples or headers. It removes the express no-filtering wording and the explanatory guidance about automatic replies, evidence resubmission and ticket continuity. Guaranteed receipt remains a requirement; the shorter wording does not establish permission to discard reports.

Validation procedure safeguards · Version 2.0 removes the explicit objectives of authenticating RIPE NCC validation requests and avoiding exclusively automated validation. It still requires confirmation that the resource holder understands the policy, monitors the mailbox, takes measures and responds to reports. The initial and escalation periods remain capped at 15 days each, with escalation now expressly directed to other LIR contacts.

Non-binding implementation example · Version 2.0 omits the earlier non-policy example involving two validation emails, a separate code, CAPTCHA, acknowledgement checkbox and invalid-contact states. Its additional-information section instead explains discretion over validation periods and frequency. This removes suggested implementation detail rather than repealing a previously binding two-email procedure.

Regional comparison · The historical comparison changes ARIN from a region where a similar proposal was under discussion to one where it was abandoned. APNIC remains listed as having accepted a similar proposal, while LACNIC and AFRINIC remain under discussion. These are statements in the compared snapshots, not a claim about current regional policy.

3.0
철회됨 · Withdrawn
2020. 4. 15.
출처 정보 ↗

Scope of mailbox validation · Version 3.0 narrows validation to whether the abuse-mailbox attribute is present and can receive messages. It expressly excludes checking how abuse cases are processed and says the intent is not to examine mailbox monitoring or case handling. This replaces version 2.0's confirmation that the holder monitors the mailbox, takes measures and responds to reports.

Validation timing and escalation · Version 3.0 retains a six-month default but allows the RIPE NCC to change it according to contact accuracy, expressly giving a move to annual validation as an example. It omits the two explicit 15-day validation periods and the express creation/update validation trigger from version 2.0, while retaining follow-up under relevant RIPE policies and procedures after failure.

Abuse-report transport · The new proposed policy incorporates the requirement to receive both automatic and manual reports into the abuse-mailbox definition, names X-ARF/RFC5965/RFC6650 as automatic-report examples, and retains the prohibition on forcing the sender to use a form. The former separate requirement for recipient intervention is absent from that definition.

Community reporting and statistics · The earlier section explicitly invited reports of fraudulent or non-compliant mailbox behaviour for re-validation. Version 3.0 instead calls for community escalation/reporting so anonymised statistics can be collected and periodically published, with the additional explanation that the community can use them for further decisions. It does not retain the earlier enumerated fraud examples or promise that every such report triggers the former section 4.0 re-validation.

Appeal history · The version 3.0 snapshot adds a dated account of the proposer's 5 October 2020 appeal and the WG Chairs Collective's 26 October 2020 decision to uphold the Anti-Abuse Working Group co-chairs' decision. The version 2.0 snapshot has no corresponding appeal account. The addition records process history; it does not demonstrate adoption of the proposal.

Regional comparison · Version 3.0 describes APNIC's similar proposal as implemented and LACNIC's as accepted, keeps AFRINIC under discussion, and says ARIN has a similar policy. The preceding snapshot described LACNIC as under discussion and an ARIN proposal as abandoned. These statements are preserved as historical snapshot differences, without treating a policy's existence and a particular proposal's outcome as equivalent.

논의 연표

  1. 도입됨

    도입됨

    출처 정보 ↗
  2. 공식 버전

    1.0

    철회됨 · Withdrawn

    출처 정보 ↗
  3. 공식 버전

    2.0

    철회됨 · Withdrawn

    출처 정보 ↗
  4. 공식 버전

    3.0

    철회됨 · Withdrawn

    출처 정보 ↗
  5. 공식 결정

    withdrawn

    withdrawn

    출처 정보 ↗

참여 주체

최종 업데이트:

불러오는 중…

출처 및 적용 범위

공개 토론 기록 보관소

커버리지

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