1 / 7

EREG – IRIS for ENUM

EREG – IRIS for ENUM. Andrew Newton < andy@hxr.us > 62 th IETF, Minneapolis, MN, USA 11 – November – 2003. Quick Update. CRISP WG base requirements done protocol selection done moving forward with IRIS draft-newton-iris-ereg-01.txt incorporated comments received for –00.

missy
Download Presentation

EREG – IRIS for ENUM

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. EREG – IRIS for ENUM Andrew Newton <andy@hxr.us> 62th IETF, Minneapolis, MN, USA 11 – November – 2003

  2. Quick Update • CRISP WG • base requirements done • protocol selection done • moving forward with IRIS • draft-newton-iris-ereg-01.txt • incorporated comments received for –00. • removed cruft from section 6 • updated to be current with iris-core -04

  3. Why? • Is a whois service needed for ENUM? • Will ENUM just be a small community of providers? • Will all ENUM interactions remain intra-national? • cross-border abuse? • cross-border coordination? • Will there be delegations to private entities? • b2b & e2e coordination?

  4. Who? • Who will resolve ENUM problems? • To resolve an issue, does the end-point sys admin have to rely on the upward chain? • Who do you contact? • Large network operators have different sys admins for different purposes: abuse, noc, etc… • Which one is which? • Is that SOA a SIP address or an SMTP address or an XMPP address?

  5. What? • Just what can go wrong? • Messed up MX records are fairly common, so what’s the likelihood of encountering a messed up NAPTR or SRV record? • Will fat-fingering cause incorrect delegations or bad NS sets at the zone apex? • What will we do about abuse? • Will ENUM will be easy prey for war-dialing SIP spammers?

  6. This Proposal • Specifies a vector for coordination. • Not mandating “the” vector for coordination. • Is one part of the answer. • No protocol/technology can be the whole answer. • Policy plays a major role. • Attempts to be policy-neutral. • Providers have differing requirements based on jurisdiction.

  7. Applicability • Public-facing • account for data miners and abusive users • Privacy • pluggable authentication for adaptable authorization • Structured • well-understood multiple methods of alternative contact • I18N • localization of protocol elements • multiple language contact equivalents • standard queries and results

More Related