WHOIS UPDATES

22
WHOIS UPDATES

description

WHOIS UPDATES. Three Main Updates. DNSSEC Deployment Full support for ASPLAIN Abuse Contact Implementation. DNSSEC. DNSSEC. One part of DNSSEC deployment plan M inor change in WHOIS ds- rdata attribute Two methods for updating this field Via MyAfrinic (with verification) - PowerPoint PPT Presentation

Transcript of WHOIS UPDATES

Page 1: WHOIS UPDATES

WHOIS UPDATES

Page 2: WHOIS UPDATES

- DNSSEC Deployment

- Full support for ASPLAIN

- Abuse Contact Implementation

Three Main Updates

Page 3: WHOIS UPDATES

DNSSEC

Page 4: WHOIS UPDATES

DNSSEC

- One part of DNSSEC deployment plan- Minor change in WHOIS - ds-rdata attribute- Two methods for updating this field

- Via MyAfrinic (with verification)- [email protected] (without verification)

Page 5: WHOIS UPDATES

Domain Object template

DNSSEC

Page 6: WHOIS UPDATES

Reverse Delegation on MyAFRINIC

DNSSEC

Page 7: WHOIS UPDATES

Example of Domain object on WHOISDNSSEC

Page 8: WHOIS UPDATES

ASPLAIN

Page 9: WHOIS UPDATES

- Full Support for 4-Byte ASN- Scrap out the dot format

- <high order 16 bit value in decimal>.<low order 16 bit value in decimal>

- 4-byte AS Number of value 65546 (decimal) would be identified as "1.10”

- Both WHOIS and Myafrinic support this format

ASPLAIN

Page 10: WHOIS UPDATES

Example of previously AS5.1 in plain format

ASPLAIN

Page 11: WHOIS UPDATES

Abuse contact Policy

Page 12: WHOIS UPDATES

Abuse Contact Policy AFPUB-2010-GEN-006 Recommendations:

For abuse reports to reach the correct network contact

Create a new or uses an already existing object A unique reference by inetnum, inet6num and

aut-num Contains 2 email attributes: "e-mail:" for personal communication "abuse-mailbox:" for automatic report handling

Page 13: WHOIS UPDATES

Abuse Contact Policy - Use existing Incident Response Team Object

Page 14: WHOIS UPDATES

Abuse Contact PolicyIRT Object

- Field: abuse-mailbox Abuse Contact email addressMandatoryMultiple

- whois -i abuse-mailbox <email>

- Field: emailAbuse Contact email addressMandatoryMultiple

Page 15: WHOIS UPDATES

Abuse Contact PolicyIRT Object

Field: auth Authentication credentials

Password or PGP Key Used when adding or removing a reference to inetnum,

inet6num or aut-num objects Mandatory Multiple

whois -i auth <email>

Page 16: WHOIS UPDATES

Abuse Contact Policy

IRT Object Field: irt-nfy Notify email address Optional Multiple

whois -i irt-nfy <email>

Page 17: WHOIS UPDATES

Abuse Contact Policy

]

Page 18: WHOIS UPDATES

Abuse Contact Policy

INETNUM Object Field: mnt-irt Reference an IRT object Optional Multiple

whois -i mnt-irt <IRT ID> Similarly in INET6NUM and AUT-NUM

Page 19: WHOIS UPDATES

INETNUMOBJECT

IRTOBJECT

Abuse Contact Policy

INETNUM’s maintainer authentication AND

IRT object’s authentication(Password / PGP Key)

INETNUM referencing an IRT Object

Referencing an IRT Object

Page 20: WHOIS UPDATES

WAY FORWARD

Page 21: WHOIS UPDATES

- we are closely following the WEIRDS mailing list

- dev-team is looking into technologies to build RESTFUL services around whois

Page 22: WHOIS UPDATES

THANK YOU

AFRINIC DEV-TEAM