UA-Ready: Ry-Rr Considerations Excerpts from a case study Richard - - PowerPoint PPT Presentation

ua ready ry rr considerations
SMART_READER_LITE
LIVE PREVIEW

UA-Ready: Ry-Rr Considerations Excerpts from a case study Richard - - PowerPoint PPT Presentation

UA-Ready: Ry-Rr Considerations Excerpts from a case study Richard Merdinger, Go Daddy Dennis Tan Tanaka, Verisign Eating your own dog food! Approach 100% open discussion Confidential Collaborative Developmental Identified


slide-1
SLIDE 1

Excerpts from a case study

UA-Ready: Ry-Rr Considerations

Richard Merdinger, Go Daddy Dennis Tan Tanaka, Verisign

slide-2
SLIDE 2

Eating your own dog food!

slide-3
SLIDE 3

Approach

  • 100% open discussion
  • Confidential
  • Collaborative
  • Developmental
  • Identified core system elements
  • Engaged Internal Experts
  • Painstakingly reviewed details
  • Extrapolated issues to apply broadly
slide-4
SLIDE 4

What’s Involved?

  • System Integration
  • Data Integrity
  • Customer Data
  • Customer Communication
  • Policy Compliance
  • Customer Satisfaction
slide-5
SLIDE 5

System Integration

  • EPP is already UA-friendly
  • Surprisingly few elements require special handling
  • Some do…
  • Most important: host names and labels
  • System configuration complexities
slide-6
SLIDE 6

Data Integrity

  • Don’t make assumptions
  • Be explicit
  • A-label/U-label usage
  • Have a defined defaults
  • Robust implementations
  • Be prepared to validate input
  • Handle exceptions
  • Enforce Storage fidelity
slide-7
SLIDE 7

Customer Data

  • Input from customer is unpredictable
  • Contact data includes UTF-8 Data

(RFC5730 recommends use of UTF-8)

  • Current Whois does not support it
  • Validation and homogenization necessary
  • Develop processes to deal with issues that cannot

be immediately remedied

slide-8
SLIDE 8

Customer Communication

  • Where UA-Readiness hits home
  • When possible, have multiple means of

communication

  • Troubleshooting EAI issues via email not reliable
slide-9
SLIDE 9

Policy Compliance

  • UA-Readiness can prevent RAA compliance

relative to Registrant Validation

  • New policies increasingly rely on being able to

contact Registrants (e.g., IRTP)

  • “Real Name Validation” in China and other regions

could also be affected

slide-10
SLIDE 10

Customer Satisfaction

  • We provide Domains – Our products have to work
  • Failure to do so could lead to alternate

technologies being developed

  • UA-UNReadiness = Customer DISSatisfaction
slide-11
SLIDE 11

It’s still early…or is it?

  • New gTLDs are not new…we’re really in Round 4
  • IDNs are a reality
  • EAI is a reality
  • Ry-Rr UA issues are everyone’s issues
slide-12
SLIDE 12

Q&A