The Public Suffix Structure file format and its use for Cookie domain validation
draft-pettersen-subtld-structure-08
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Expired".
Expired & archived
|
|
|---|---|---|---|
| Author | Yngve Pettersen | ||
| Last updated | 2011-07-11 (Latest revision 2011-03-14) | ||
| RFC stream | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
This document defines the term "Public Suffix" as meaning a domain under which multiple parties that are unaffiliated with the owner may register subdomains. Examples of Public Suffixes include "org", "co.uk" and "k12.wa.us". It also defines a fileformat that can be used to distribute information about such Public Suffixes to relying parties. As an example, this information is then used to limit which domains an Internet service can set cookies for, strengthening the rules already defined by the cookie specifications. This specification updates RFC 6265 [RFC6265] by defining the term "Public Suffix".
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)