From 10b4ec2da511b2380d6e0ff697e1cc21ea6d8e49 Mon Sep 17 00:00:00 2001
From: Sabela <sabela.delatorre@crg.eu>
Date: Fri, 28 Sep 2018 11:45:03 +0200
Subject: [PATCH] Change MUST with SHOULD as we agreed in the security review
 meetiing.

---
 beacon.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/beacon.md b/beacon.md
index f50328e6..b0c3f071 100644
--- a/beacon.md
+++ b/beacon.md
@@ -21,7 +21,7 @@ Due to the needs for data discoverability providing as much metadata as possible
 
 ## Protocol essentials
 
-Beacon provides REST API on top of the HTTPS protocol, as specified in RFC 7231. HTTPS (HTTP over SSL) MUST be used instead of regular HTTP because the communication between Beacon server and Beacon client has to be encrypted. The Beacon API has two endpoints: `/` (also known as _Info endpoint_) and `/query`. The _Info endpoint_ provides general metadata about the Beacon instance and dataset(s) included. The query interface is provided by the _Query endpoint_. 
+Beacon provides REST API on top of the HTTPS protocol, as specified in RFC 7231. HTTPS (HTTP over SSL) SHOULD be used instead of regular HTTP because the communication between Beacon server and Beacon client has to be encrypted. The Beacon API has two endpoints: `/` (also known as _Info endpoint_) and `/query`. The _Info endpoint_ provides general metadata about the Beacon instance and dataset(s) included. The query interface is provided by the _Query endpoint_. 
 
 The full complement of Beacon API endpoints, requests and responses is published in [OpenAPI format](https://github.com/ga4gh-beacon/specification/blob/master/beacon.yaml).