• Like
Addressing non-FQDNs and new gTLDs in SSL Baseline Requirements
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

Addressing non-FQDNs and new gTLDs in SSL Baseline Requirements

  • 197 views
Published

CA/Browser Forum RSA deck on non FQDNs and new gTLDs

CA/Browser Forum RSA deck on non FQDNs and new gTLDs

Published in Technology
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
    Be the first to like this
No Downloads

Views

Total Views
197
On SlideShare
0
From Embeds
0
Number of Embeds
2

Actions

Shares
Downloads
1
Comments
0
Likes
0

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

  • 1. CA/Browser Forum
  • 2. May 2009 - ICANN should consider expanding reserved names of RFC 2606 to include commonly used internal TLDs, such as .internal, .local, .private, .corp, .home May 2011 – CABF announces public review of Baseline Requirements with plan to sunset internal names July 2012 – Baseline Requirements effective – CA must notify customers that non-FQDNs deprecated Nov. 1, 2015 – No Issuance of Certificates with non-FQDNs October 1, 2016 - All Internal Name Certificates revoked February 2013 – Ballot 96 amends Baseline Requirements
  • 3. CA shouldn’t issue certificate with proposed gTLD CA must warn applicant that certificates with applied-for gTLD will be revoked when approved 30 days to review existing certificates and cease issuing certificates containing new gTLD 120 days to revoke certificate containing new gTLD Unless Applicant entitled to use domain under new gTLD
  • 4. https://www.cabforum.org/GuidanceDeprecated-Internal-Names.pdf Ben Wilson, CA/Browser Forum www.cabforum.org