/
284.txt
112 lines (77 loc) · 3.78 KB
/
284.txt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
[17] [DFN[eTLD+1]] は、同一の管理主体の管理下にあると思われる[[ドメイン名]]空間の単位です。
[[Web]] においては[[起源]]の次に大きな[[セキュリティー]]その他の制御上の重要な構造として扱われています。
* 仕様書
[REFS[
- [2] [CITE@en[Storage Standard]] ([TIME[2015-11-18 18:41:19 +09:00]] 版) <https://storage.spec.whatwg.org/#site>
]REFS]
* 意味
;; [6] [[PSL]] も参照。
* 文脈
@@
[4] [[Storage Standard]]
[5] [[Web Storage]] のサイズ制限 ([[ストレージ (Web)]] 参照)。
* ドメイン名用語として
[13] [[public suffix]] に一階層加えた[[ドメイン]]を、
[DFN[naked domain]]、[DFN[apex domain]]、[DFN[zone apex]]、[DFN[root domain]]
などと呼ぶことがあります。
[EG[
[14] [CODE[example.com]] は [[naked domain]] です。 [CODE[www.example.com]] は
[[naked domain]] ではありません。
]EG]
;; [15] [[DNS]] では [[TLD]] より上位の名前の無い階層 ([CODE[.]]) のことを [[root domain]]
と呼んでおり、 [[naked domain]] のことを [[root domain]] と呼ぶのは適切ではありません。
[16] 「[CODE[CNAME]] を使えない」といった話題でよく使われる用語です。
* 歴史
[FIG(quote)[
[FIGCAPTION[
[1] [CITE[IRC logs: freenode / #whatwg / 20150911]]
([TIME[2015-09-12 14:18:28 +09:00]] 版)
<http://krijnhoetmer.nl/irc-logs/whatwg/20150911>
]FIGCAPTION]
> # '''['''09:47''']''' <annevk> I want a term for eTLD+1, I was thinking "site" but a URL's site just seems rather wrong
> # '''['''09:48''']''' <annevk> That's one of the things blocking a more formal definition of public suffixes in URL
]FIG]
[3] [CITE@en[Allow POSTs to same eTLD+1 endpoints. · w3c/webappsec-credential-management@d30032e]]
([TIME[2016-02-19 15:48:33 +09:00]] 版)
<https://github.com/w3c/webappsec-credential-management/commit/d30032e1a439089460a6801987a7748d8d6de010>
[FIG(quote)[
[FIGCAPTION[
[7] [CITE@en[RFC 7489 - Domain-based Message Authentication, Reporting, and Conformance (DMARC)]]
( ([TIME[2016-05-31 06:53:47 +09:00]]))
<https://tools.ietf.org/html/rfc7489#section-3.2>
]FIGCAPTION]
>
> Thus, since "com" is an IANA-registered TLD, a subject domain of
> "a.b.c.d.example.com" would have an Organizational Domain of
> "example.com".
]FIG]
[FIG(quote)[
[FIGCAPTION[
[8] [CITE@en[View the Public Suffix List]]
( ([TIME[2016-05-05 01:22:01 +09:00]]))
<https://publicsuffix.org/list/>
]FIGCAPTION]
> The registered or registrable domain is the public suffix plus one additional label.
]FIG]
[9] [CITE@en[Re: VC meeting to discuss Permissions spec]]
( ([[Anne van Kesteren]]著, [TIME[2016-06-09 18:35:56 +09:00]]))
<https://lists.w3.org/Archives/Public/public-webappsec/2016Jun/0036.html>
[FIG(quote)[
[FIGCAPTION[
[10] [CITE@en[publicsuffix: cannot derive eTLD+1 for domain "s3.cn-north-1.amazonaws.com.cn" · Issue #14734 · golang/go]]
( ([TIME[2016-06-10 18:14:03 +09:00]]))
<https://github.com/golang/go/issues/14734>
]FIGCAPTION]
> "s3.cn-north-1.amazonaws.com.cn" is in https://publicsuffix.org/list/public_suffix_list.dat , so I think this is working as intended.
]FIG]
[FIG(quote)[
[FIGCAPTION[
[11] [CITE@en[Web Authentication: An API for accessing Scoped Credentials]]
( ([TIME[2016-06-02 01:04:34 +09:00]]))
<https://w3c.github.io/webauthn/#etld1>
]FIGCAPTION]
> Also known as a Registered Domain '''['''PSL''']''', an eTLD+1 is an effective Top-Level Domain Name (eTLD), plus the next domain name label, proceding from right to left.
]FIG]
[12] [CITE@en[Clear entire eTLD+1 for cookies.]]
([[@annevk]]著, [TIME[2016-07-20 19:57:38 +09:00]])
<https://github.com/w3c/webappsec-clear-site-data/commit/9b510bfa74223535670aba8a00177af883b28a8a>