@@ 2,7 2,7 @@
title = {基於 {Kubernetes} 個別用戶資源管控之 {PaaS} 平台},
author = {周詳},
year = {2021},
- month = {January},
+ month = jan,
school = {國立交通大學},
type = {Master's thesis},
}
@@ 11,24 11,23 @@
title = {基於 {Kubernetes} 使用者專案管理之 {PaaS} 平台},
author = {李宗緯},
year = {2022},
- month = {August},
+ month = aug,
school = {國立陽明交通大學},
type = {Master's thesis},
}
-% XXX quotes missing on online/electornic in IEEEtran
% TODO dot position, urldate, unify rfcs
-@online{kubernetes,
- title = {``{Kubernetes}''},
+@misc{kubernetes,
+ title = {{Kubernetes}},
author = {{The Kubernetes Authors}},
year = {2024},
url = {https://kubernetes.io/},
urldate = {2024-09-23},
}
-@online{helm,
- title = {``{Helm}''},
+@misc{helm,
+ title = {{Helm}},
author = {{Helm Authors}},
year = {2024},
url = {https://helm.sh/},
@@ 43,50 42,66 @@
year = {2017},
}
-@online{cel,
- title = {``{CEL}''},
+@misc{cel,
+ title = {{CEL}},
author = {{Google LLC}},
year = {2024},
url = {https://cel.dev/},
urldate = {2024-09-24},
}
-@online{kubebuilder,
- title = {``{Introduction} - The {Kubebuilder} Book''},
+@misc{kubebuilder,
+ title = {{Introduction} - The {Kubebuilder} Book},
author = {{The Kubernetes Authors}},
year = {2024},
url = {https://book.kubebuilder.io/introduction},
urldate = {2024-09-23},
}
-@online{vue,
- title = {``{Vue.js} - The Progressive {JavaScript} Framework''},
+@misc{vue,
+ title = {{Vue.js} - The Progressive {JavaScript} Framework},
author = {Evan You},
year = {2024},
url = {https://vuejs.org/},
urldate = {2024-09-23},
}
-@techreport{fette2011websocket,
- title = {The {WebSocket} protocol},
- author = {Fette, Ian and Melnikov, Alexey},
- year = {2011},
-}
-
-@article{jones2015json,
- title = {{JSON Web Token (JWT)}},
- author = {Jones, Michael},
- journal = {Internet Engineering Task Force (IETF) RFC},
- volume = {7519},
- year = {2015},
-}
-
-@article{sakimura2014openid,
- title = {{OpenID Connect Core} 1.0 incorporating errata set 1},
+@misc{rfc6455,
+ series = {Request for Comments},
+ number = 6455,
+ howpublished = {RFC 6455},
+ publisher = {RFC Editor},
+ doi = {10.17487/RFC6455},
+ url = {https://www.rfc-editor.org/info/rfc6455},
+ author = {Alexey Melnikov and Ian Fette},
+ title = {{The WebSocket Protocol}},
+ pagetotal = 71,
+ year = 2011,
+ month = dec,
+ abstract = {The WebSocket Protocol enables two-way communication between a client running untrusted code in a controlled environment to a remote host that has opted-in to communications from that code. The security model used for this is the origin-based security model commonly used by web browsers. The protocol consists of an opening handshake followed by basic message framing, layered over TCP. The goal of this technology is to provide a mechanism for browser-based applications that need two-way communication with servers that does not rely on opening multiple HTTP connections (e.g., using XMLHttpRequest or \textless{}iframe\textgreater{}s and long polling). {[}STANDARDS-TRACK{]}},
+}
+
+@misc{rfc7519,
+ series = {Request for Comments},
+ number = 7519,
+ howpublished = {RFC 7519},
+ publisher = {RFC Editor},
+ doi = {10.17487/RFC7519},
+ url = {https://www.rfc-editor.org/info/rfc7519},
+ author = {Michael B. Jones and John Bradley and Nat Sakimura},
+ title = {{JSON Web Token (JWT)}},
+ pagetotal = 30,
+ year = 2015,
+ month = may,
+ abstract = {JSON Web Token (JWT) is a compact, URL-safe means of representing claims to be transferred between two parties. The claims in a JWT are encoded as a JSON object that is used as the payload of a JSON Web Signature (JWS) structure or as the plaintext of a JSON Web Encryption (JWE) structure, enabling the claims to be digitally signed or integrity protected with a Message Authentication Code (MAC) and/or encrypted.},
+}
+
+@misc{oidc,
+ title = {{OpenID Connect Core} 1.0 incorporating errata set 2},
author = {Sakimura, Nat and Bradley, John and Jones, Mike and De Medeiros, Breno and Mortimore, Chuck},
- journal = {The OpenID Foundation, specification},
- volume = {335},
- year = {2014},
+ year = {2023},
+ url = {https://openid.net/specs/openid-connect-core-1_0.html},
+ urldate = {2024-09-23},
}
@inproceedings{swaminathan2011low,
@@ 98,16 113,34 @@
organization = {IEEE},
}
-@techreport{cooper2008internet,
- title = {Internet {X.509} public key infrastructure certificate and certificate revocation list {(CRL)} profile},
- author = {Cooper, David and Santesson, Stefan and Farrell, Stephen and Boeyen, Sharon and Housley, Russell and Polk, William},
- year = {2008},
-}
-
-@techreport{santesson2013x,
- title = {{X.509} {Internet} public key infrastructure online certificate status protocol - {OCSP}},
- author = {Santesson, Stefan and Myers, Michael and Ankney, Rich and Malpani, Ambarish and Galperin, Slava and Adams, Carlisle},
- year = {2013},
+@misc{rfc5280,
+ series = {Request for Comments},
+ number = 5280,
+ howpublished = {RFC 5280},
+ publisher = {RFC Editor},
+ doi = {10.17487/RFC5280},
+ url = {https://www.rfc-editor.org/info/rfc5280},
+ author = {Sharon Boeyen and Stefan Santesson and Tim Polk and Russ Housley and Stephen Farrell and David Cooper},
+ title = {{Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile}},
+ pagetotal = 151,
+ year = 2008,
+ month = may,
+ abstract = {This memo profiles the X.509 v3 certificate and X.509 v2 certificate revocation list (CRL) for use in the Internet. An overview of this approach and model is provided as an introduction. The X.509 v3 certificate format is described in detail, with additional information regarding the format and semantics of Internet name forms. Standard certificate extensions are described and two Internet-specific extensions are defined. A set of required certificate extensions is specified. The X.509 v2 CRL format is described in detail along with standard and Internet-specific extensions. An algorithm for X.509 certification path validation is described. An ASN.1 module and examples are provided in the appendices. {[}STANDARDS-TRACK{]}},
+}
+
+@misc{rfc6960,
+ series = {Request for Comments},
+ number = 6960,
+ howpublished = {RFC 6960},
+ publisher = {RFC Editor},
+ doi = {10.17487/RFC6960},
+ url = {https://www.rfc-editor.org/info/rfc6960},
+ author = {Stefan Santesson and Michael Myers and Rich Ankney and Ambarish Malpani and Slava Galperin and Dr. Carlisle Adams},
+ title = {{X.509 Internet Public Key Infrastructure Online Certificate Status Protocol - OCSP}},
+ pagetotal = 41,
+ year = 2013,
+ month = jun,
+ abstract = {This document specifies a protocol useful in determining the current status of a digital certificate without requiring Certificate Revocation Lists (CRLs). Additional mechanisms addressing PKIX operational requirements are specified in separate documents. This document obsoletes RFCs 2560 and 6277. It also updates RFC 5912.},
}
@inproceedings{spies2021evaluation,
@@ 129,7 162,7 @@
publisher = {HeinOnline},
}
-@online{openapi,
+@misc{openapi,
title = {{OpenAPI} Specification v3.0.0},
author = {Whitlock, Jeremy and Gardiner, Marsh and Ratovsky, Ron and Tam, Tony and Harmon, Jason},
year = {2017},
@@ 145,7 178,7 @@
year = {2016},
}
-@online{yaml,
+@misc{yaml,
title = {{YAML} ain't markup language {(YAML™)} version 1.2, revision 1.2.2},
author = {Ben-Kiki, Oren and Evans, Clark and döt Net, Ingy},
year = {2021},
@@ 153,9 186,17 @@
urldate = {2024-09-25},
}
-@misc{bray2017rfc,
- title = {{RFC} 8259: The {JavaScript} object notation {(JSON)} data interchange format},
- author = {Bray, Tim},
- year = {2017},
- publisher = {RFC Editor},
+@misc{rfc8259,
+ series = {Request for Comments},
+ number = 8259,
+ howpublished = {RFC 8259},
+ publisher = {RFC Editor},
+ doi = {10.17487/RFC8259},
+ url = {https://www.rfc-editor.org/info/rfc8259},
+ author = {Tim Bray},
+ title = {{The JavaScript Object Notation (JSON) Data Interchange Format}},
+ pagetotal = 16,
+ year = 2017,
+ month = dec,
+ abstract = {JavaScript Object Notation (JSON) is a lightweight, text-based, language-independent data interchange format. It was derived from the ECMAScript Programming Language Standard. JSON defines a small set of formatting rules for the portable representation of structured data. This document removes inconsistencies with other specifications of JSON, repairs specification errors, and offers experience-based interoperability guidance.},
}