-
Notifications
You must be signed in to change notification settings - Fork 4
/
284.txt
161 lines (113 loc) · 6 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
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
[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>
[18] [CITE@en[For users on very slow connections, block document.written scripts · Issue #17 · WICG/interventions]]
([TIME[2016-10-25 13:13:46 +09:00]])
<https://github.com/WICG/interventions/issues/17>
[FIG(quote)[
[FIGCAPTION[
[19] [CITE@ja-JP[AWS | Elastic Load Balancing | Classic Load Balancer のよくある質問]]
( ([TIME[2016-12-02 11:11:38 +09:00]]))
<https://aws.amazon.com/jp/elasticloadbalancing/classicloadbalancer/faqs/>
]FIGCAPTION]
> Q: 自分のドメイン (例えば、http://example.com) の zone apex へのトラフィックのロードバランスを実行できますか?
> はい。詳細については、Elastic Load Balancing 開発者ツールをご参照ください。
]FIG]
[20] [CITE@en[For users on very slow connections, block document.written scripts · Issue #17 · WICG/interventions]]
([TIME[2017-07-15 23:59:49 +09:00]])
<https://github.com/WICG/interventions/issues/17>
[21] [CITE[Intelligent Tracking Prevention | WebKit]]
([TIME[2017-09-26 23:23:28 +09:00]])
<https://webkit.org/blog/7675/intelligent-tracking-prevention/>
[22] [CITE@en[Define hosts' public suffix and registrable domain, as well as same site]]
([[mikewest]]著, [TIME[2018-06-07 18:11:56 +09:00]])
<https://github.com/whatwg/url/commit/6a9f7eacaae962b325547f33d6e30134789986a8>
[23] [CITE@en[Define hosts' public suffix and registrable domain. by mikewest · Pull Request #391 · whatwg/url]]
([TIME[2018-06-13 22:13:23 +09:00]])
<https://github.com/whatwg/url/pull/391>
[24] [CITE@en[Build upon URL rather than PSL]]
([[annevk]]著, [TIME[2018-06-07 18:31:20 +09:00]])
<https://github.com/whatwg/html/commit/326c64415ddff5f619433028bd5d99408dad6430>
[25] [CITE@en[Define Cross-Origin-Resource-Policy response header]]
([[annevk]]著, [TIME[2018-06-18 22:36:30 +09:00]])
<https://github.com/whatwg/fetch/commit/0cec471b1ba938d775415e2ea08a2d2be4e72413>
[26] [CITE[Intelligent Tracking Prevention 2.0 | WebKit]]
([TIME[2018-06-21 02:16:10 +09:00]])
<https://webkit.org/blog/8311/intelligent-tracking-prevention-2-0/>
[27] [CITE@en[Restructure URL rendering section and add additional guidance]]
([[estark37]]著, [TIME[2019-04-04 23:49:46 +09:00]])
<https://github.com/whatwg/url/commit/8809598ddfd1d935432c8a0cad53f13d70e24bc6>