Skip to content

Commit

Permalink
Updated news
Browse files Browse the repository at this point in the history
  • Loading branch information
phax committed Feb 16, 2024
1 parent c7b729a commit 8cea008
Show file tree
Hide file tree
Showing 3 changed files with 7 additions and 5 deletions.
8 changes: 4 additions & 4 deletions docs/specification/2-changelog.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -5,10 +5,10 @@
== Version 2.0.3 (2024-02-16)

* Renamed "OpenPEPPOL" to "OpenPeppol"
* Fixed broken links inside the document
* Updated eDEC References
* Unified table headings
* Unified table layouts
* Fixed broken links inside the document and in the references
* Updated versions of eDEC References
* Added missing references to RFC 2119, RFC 7230 and Peppol Policy for Transport Security
* Unified table headings and layouts

== Version 2.0.2 (2021-04-13)

Expand Down
2 changes: 2 additions & 0 deletions docs/specification/8-references.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -15,6 +15,8 @@

* [[[PEPPOL-Envelope]]] OpenPeppol Business Message Envelope (SBDH), Version 2.0.1, 17 August 2023, https://docs.peppol.eu/edelivery/envelope/Peppol-EDN-Business-Message-Envelope-2.0.1-2023-08-17.pdf

* [[[PEPPOL-TS-POL]]] Peppol Policy for Transport Security, Version 1.1.0, 20 April 2020, https://docs.peppol.eu/edelivery/policies/PEPPOL-EDN-Policy-for-Transport-Security-1.1.0-2020-04-20.pdf

* [[[TIA-AP-PROV]]] Peppol Service Provider Agreement, Version v4.0.1, 23 June 2022, https://openpeppol.atlassian.net/wiki/spaces/AF/pages/2889089036/Peppol+Agreements

* [[[RFC2119]]] Key words for use in RFCs to Indicate Requirement Levels, March 1997, https://datatracker.ietf.org/doc/html/rfc2119
Expand Down
2 changes: 1 addition & 1 deletion docs/specification/peppol/02-transport-level-security.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -10,4 +10,4 @@ In the Peppol network the access point MUST be configured according to the follo
* Port *443 MUST* be used for TLS.
* Sending access points need only to allow outbound transmissions to port *443*.
TLS MUST use a valid certificate compliant with the Peppol Policy for transport security.
TLS MUST use a valid certificate compliant with the Peppol Policy for Transport Security (see <<PEPPOL-TS-POL>>).

0 comments on commit 8cea008

Please sign in to comment.