U bent hier
Let’s Encrypt had a great year in 2017. We more than doubled the number of active (unexpired) certificates we service to 46 million, we just about tripled the number of unique domains we service to 61 million, and we did it all while maintaining a stellar security and compliance track record. Most importantly though, the Web went from 46% encrypted page loads to 67% according to statistics from Mozilla - a gain of 21% in a single year - incredible. We’re proud to have contributed to that, and we’d like to thank all of the other people and organizations who also worked hard to create a more secure and privacy-respecting Web.
While we’re proud of what we accomplished in 2017, we are spending most of the final quarter of the year looking forward rather than back. As we wrap up our own planning process for 2018, I’d like to share some of our plans with you, including both the things we’re excited about and the challenges we’ll face. We’ll cover service growth, new features, infrastructure, and finances.Service Growth
We are planning to double the number of active certificates and unique domains we service in 2018, to 90 million and 120 million, respectively. This anticipated growth is due to continuing high expectations for HTTPS growth in general in 2018.
Let’s Encrypt helps to drive HTTPS adoption by offering a free, easy to use, and globally available option for obtaining the certificates required to enable HTTPS. HTTPS adoption on the Web took off at an unprecedented rate from the day Let’s Encrypt launched to the public.
One of the reasons Let’s Encrypt is so easy to use is that our community has done great work making client software that works well for a wide variety of platforms. We’d like to thank everyone involved in the development of over 60 client software options for Let’s Encrypt. We’re particularly excited that support for the ACME protocol and Let’s Encrypt is being added to the Apache httpd server.
Other organizations and communities are also doing great work to promote HTTPS adoption, and thus stimulate demand for our services. For example, browsers are starting to make their users more aware of the risks associated with unencrypted HTTP (e.g. Firefox, Chrome). Many hosting providers and CDNs are making it easier than ever for all of their customers to use HTTPS. Government agencies are waking up to the need for stronger security to protect constituents. The media community is working to Secure the News.New Features
We’ve got some exciting features planned for 2018.
First, we’re planning to introduce an ACME v2 protocol API endpoint and support for wildcard certificates along with it. Wildcard certificates will be free and available globally just like our other certificates. We are planning to have a public test API endpoint up by January 4, and we’ve set a date for the full launch: Tuesday, February 27.
Later in 2018 we plan to introduce ECDSA root and intermediate certificates. ECDSA is generally considered to be the future of digital signature algorithms on the Web due to the fact that it is more efficient than RSA. Let’s Encrypt will currently sign ECDSA keys from subscribers, but we sign with the RSA key from one of our intermediate certificates. Once we have an ECDSA root and intermediates, our subscribers will be able to deploy certificate chains which are entirely ECDSA.Infrastructure
Our CA infrastructure is capable of issuing millions of certificates per day with multiple redundancy for stability and a wide variety of security safeguards, both physical and logical. Our infrastructure also generates and signs nearly 20 million OCSP responses daily, and serves those responses nearly 2 billion times per day. We expect issuance and OCSP numbers to double in 2018.
Our physical CA infrastructure currently occupies approximately 70 units of rack space, split between two datacenters, consisting primarily of compute servers, storage, HSMs, switches, and firewalls.
When we issue more certificates it puts the most stress on storage for our databases. We regularly invest in more and faster storage for our database servers, and that will continue in 2018.
We’ll need to add a few additional compute servers in 2018, and we’ll also start aging out hardware in 2018 for the first time since we launched. We’ll age out about ten 2u compute servers and replace them with new 1u servers, which will save space and be more energy efficient while providing better reliability and performance.
We’ll also add another infrastructure operations staff member, bringing that team to a total of six people. This is necessary in order to make sure we can keep up with demand while maintaining a high standard for security and compliance. Infrastructure operations staff are systems administrators responsible for building and maintaining all physical and logical CA infrastructure. The team also manages a 24/7/365 on-call schedule and they are primary participants in both security and compliance audits.Finances
We pride ourselves on being an efficient organization. In 2018 Let’s Encrypt will secure a large portion of the Web with a budget of only $3.0M. For an overall increase in our budget of only 13%, we will be able to issue and service twice as many certificates as we did in 2017. We believe this represents an incredible value and that contributing to Let’s Encrypt is one of the most effective ways to help create a more secure and privacy-respecting Web.
Our 2018 fundraising efforts are off to a strong start with Platinum sponsorships from Mozilla, Akamai, OVH, Cisco, Google Chrome and the Electronic Frontier Foundation. The Ford Foundation has renewed their grant to Let’s Encrypt as well. We are seeking additional sponsorship and grant assistance to meet our full needs for 2018.
We had originally budgeted $2.91M for 2017 but we’ll likely come in under budget for the year at around $2.65M. The difference between our 2017 expenses of $2.65M and the 2018 budget of $3.0M consists primarily of the additional infrastructure operations costs previously mentioned.Support Let’s Encrypt
We depend on contributions from our community of users and supporters in order to provide our services. If your company or organization would like to sponsor Let’s Encrypt please email us at email@example.com. We ask that you make an individual contribution if it is within your means.
We’re grateful for the industry and community support that we receive, and we look forward to continuing to create a more secure and privacy-respecting Web!
The first Terminology Summit of the European Association for Terminology (EAFT) took place in Brussels (Belgium) fifteen years ago in 2002 and the Declaration for International Cooperation on Terminology, signed on June 15, was one of its key outcomes, as it gathered a series of principles and actions to promote “special language communication based on multilingualism”. The idea behind this document was to showcase Terminology in society as a whole and provide a useful tool that could be used in different contexts.
It is important to include it in this blog as permanent reference, and it is also a good opportunity to take a quick look at some highlights. The declaration starts by saying that the signing representatives consider that “terminology is omnipresent in all human activity”. This is certainly a useful fact when we are selling Terminology, and a phrase that has to be repeated over and over again if we want to keep giving Terminology the place that it deserves.
Another element of the Declaration points out to the value of terminology “as a tool for communication and transfer of knowledge” and that we need to make professionals and decision-makers aware of this fact—not an easy task when we are trying to sell terminology! However, I think that the Declaration is indeed a good tool for us to prove that managing terminology effectively and efficiently is a great investment towards delivering high-quality translations and technical documentation.
The second part of the Declaration encourages States and governments, intergovernmental bodies and international organizations to get involved in language policies and it offers 13 suggested lines of action to achieve this purpose. Although it focuses on the work that needs to be done by those entities —e.g., establish policies and funding—I believe that we, as individuals, can take it as a guideline to bring the Declaration to our own realities.
We can make alliances with peers to find new ways to collaborate with each other by sharing experiences, initiatives, and projects. We can raise awareness on the importance of doing systematic terminology work. We can create initiatives to promote the use of terminology in our field. We can help encourage multilingualism. We can share terminologies with colleagues/peers. If we cannot afford travel, we can follow international activities in social media. If you work in the academics field, you can try to encourage authorities to include Terminology in translation curricula (or in the industry that you are working).
If you want to read the full text (it’s just two pages), you can download it here (see below) or visit EAFT’s website.
The post The Brussels Declaration – for international cooperation on terminology appeared first on In My Own Terms.
Graag delen wij de conceptversie handreiking webarchivering: deel 1, publiekscommunicatie. Afgelopen maanden hebben we met diverse partners hard gewerkt aan deze handreiking. Momenteel zetten we de puntjes op de i, maar we wilden al graag deze conceptversie via dit kennisplatform inzichtelijk maken.
We nodigen jullie van harte uit om via dit platform samen in discussie te gaan over dit concept. Het is nadrukkelijk een concept. We willen jullie dan ook vragen om inhoudelijke suggesties en wijzigingsvoorstellen nog even vast te houden. We hopen namelijk in januari de eerste officiële versie te presenteren. Die versie stellen we ook beschikbaar voor een openbare review. En dat is hét moment om de inhoudelijke suggesties en wijzigingsvoorstellen met ons te delen. Zodat we concrete verbetervoorstellen op de definitieve versie van de handreiking tegelijk en gestructureerd kunnen verwerken.
Meer informatie over de review en planning daarvan volgt.
Na de openbare review gaan we aan de slag met de geleverde feedback. Ons streven is om eind maart de definitieve versie voor vaststelling aan de standaardisatieraad van het Nationaal Archief voor te leggen.
Het document is hier te vinden in de map Handreiking Webarchivering of via de onderstaande link.
Mochten jullie vragen hebben, dan horen we het graag.
Namens het beheerteam kennisproducten van het Nationaal Archief,