December 2024 release

Author: martin-lindstrom

02 - Deployment Profile for the Swedish eID Framework.md

@@ -968,7 +968,7 @@ especially important in cases of re-use of already established security
 contexts at the Identity Provider side (Single Sign On).
 
 Each identity assertion MUST have a `<saml:Subject>` element that
-specifies the principal that is the subject of all of the statements in
+specifies the principal that is the subject of all the statements in
 the assertion.
 
 The value of the `<saml:NameID>` element under the
@@ -1505,7 +1505,7 @@ A service wishing to receive encrypted messages where SHA-1 is not used as the k
 ```
 *Example of how a service announces that it wishes that the peer uses SHA-256 as the key transport digest when encrypting using RSA-OAEP-MGF1P.*
 
-> \[*\]: Note that the use if SHA-1 in this context (both as digest algoritm and as mask generation function) is limited to providing randomness of padding data and as a hash over optional OAEP parameter data which typically is an empty string. It is not used as a hash function to assert the integrity of the encrypted data. No weaknesses of SHA-1 is is known to be relevant to its use in this context.
+> \[*\]: Note that the use if SHA-1 in this context (both as digest algoritm and as mask generation function) is limited to providing randomness of padding data and as a hash over optional OAEP parameter data which typically is an empty string. It is not used as a hash function to assert the integrity of the encrypted data. No weaknesses of SHA-1 are known to be relevant to its use in this context.
 
 <a name="normative-references"></a>
 ## 9. Normative References
@@ -1650,7 +1650,7 @@ A service wishing to receive encrypted messages where SHA-1 is not used as the k
 
 **Changes between version 1.7 and 1.8:**
 
-- Section 7.1.2 was updated to state that the requirement to include both a SAD and a SignMessage extension only applies when the requested CertType is "QC/SSCD". Voluntary use of SAD for other types of signatures (e.g. non qualified signatures) does not automatically trigger a requirement to include SignMessage.
+- Section 7.1.2 was updated to state that the requirement to include both a SAD and a SignMessage extension only applies when the requested CertType is "QC/SSCD". Voluntary use of SAD for other types of signatures (e.g., nonqualified signatures) does not automatically trigger a requirement to include SignMessage.
 
 **Changes between version 1.6 and 1.7:**
 
@@ -1667,7 +1667,7 @@ A service wishing to receive encrypted messages where SHA-1 is not used as the k
 **Changes between version 1.5 and 1.6:**
 
 - In order to facilitate algorithm interoperability between peers additions concerning "Metadata Profile for Algorithm Support" \[[SAML2MetaAlgSupport](#saml2metaalg)\] was added. Section 2.1.1 was updated with a section defining how preferred algorithms are declared in metadata, and sections 5.2, 6.1 and 7.2.1 was updated with requirements for algorithm selection during signing and encryption.
-- Section 5.3, "Message Content", was re-structured with sub-chapters for requested authentication contexts, scoping and principal selection.
+- Section 5.3, "Message Content", was re-structured with subchapters for requested authentication contexts, scoping and principal selection.
 - The `PrincipalSelection` and `RequestedPrincipalSelection` extensions were introduced to sections 2.1.3, 5.3.3 and 7.2.
 - The link for the "Tillitsramverk för Svensk e-legitimation" specification was updated.
 - This profile is no longer normatively dependent upon SAML2Int. Therefore, the profile has been updated with requirements that previously was implicit (due to the normative dependency to SAML2Int).
@@ -1713,7 +1713,7 @@ and the use of the `signMessageDigest` attribute was introduced.
 -   In section 7.1, a set of authentication context URIs for the eIDAS
     Framework was added.
 
--   In section 6.4, the requirement to use the sub-level status code
+-   In section 6.4, the requirement to use the sublevel status code
     `http://id.elegnamnden.se/status/1.0/cancel` was added. This status
     should be used to indicate a cancelled operation.
 

03 - Registry for Identifiers.md

@@ -262,7 +262,7 @@ The assurance levels defined in section [3.1.1](#authentication-context-uris) ma
 | `http://id.swedenconnect.se/loa/1.0/`<br/>`uncertified-loa2` | URI that is indented to be used by uncertified providers that make a self declaration of providing an assurance level comparable to Assurance level 2 - `http://id.elegnamnden.se/loa/1.0/loa2`. | This document |
 | `http://id.swedenconnect.se/loa/1.0/`<br/>`uncertified-loa3` | URI that is indented to be used by uncertified providers that make a self declaration of providing an assurance level comparable to Assurance level 3 - `http://id.elegnamnden.se/loa/1.0/loa3`. | This document |
 
-Proxy providers that have eIDAS authentication as an option MUST NOT use the eIDAS authentication context URIs defined in section [3.1.1](#authentication-context-uris). Instead they should use:
+Proxy providers that have eIDAS authentication as an option MUST NOT use the eIDAS authentication context URIs defined in section [3.1.1](#authentication-context-uris), instead they should use:
 
 | **URL** | **Object** | **Reference** |
 | :--- | :--- | :--- |
@@ -339,7 +339,7 @@ Service Contract Entity Category identifiers are indented for performing service
 
 All Service Contract identifiers are prefixed with `http://id.swedenconnect.se/contract/<org>`, where `org` is the identifier for the defining organization.
 
-The Sweden Connect Framework specifications do not define any Service Contract identifiers. Instead the federation operator, or other parties, may define identifiers suitable for representing how consuming and providing services should be matched based on their respective agreements.
+The Sweden Connect Framework specifications do not define any Service Contract identifiers, instead the federation operator, or other parties, may define identifiers suitable for representing how consuming and providing services should be matched based on their respective agreements.
 
 <a name="general-entity-categories"></a>
 ##### 3.1.3.5. General Entity Categories
@@ -425,7 +425,7 @@ This section defines identifiers used within the Sweden Connect Framework to int
 <a name="eidas-proxy-service-aliases"></a>
 ##### 3.1.9.1. eIDAS Proxy Service Aliases
 
-Each country within the eIDAS federation provides an eIDAS Proxy Service that is a Proxy Identity Provider for the authentication services within that specific country. The entityID identifier for an eIDAS Proxy Service in another country is not known to a Swedish Service Provider, but there are cases in which the Swedish Service Provider needs to refer to a specific eIDAS Proxy Service. Therefore, this specification defines an URI identifier format for eIDAS Proxy Service aliases. The format is as follows:
+Each country within the eIDAS federation provides an eIDAS Proxy Service that is a Proxy Identity Provider for the authentication services within that specific country. The entityID identifier for an eIDAS Proxy Service in another country is not known to a Swedish Service Provider, but there are cases in which the Swedish Service Provider needs to refer to a specific eIDAS Proxy Service. Therefore, this specification defines a URI identifier format for eIDAS Proxy Service aliases. The format is as follows:
 
 **`http://id.swedenconnect.se/eidas/1.0/proxy-service/{country-code}`**
 
@@ -583,7 +583,7 @@ Object Identifier Registry for Sweden Connect<sup>*</sup>
 
 <a name="sc-saml-umsg"></a>
 **\[SC.SAML.UMsg\]**
-> [User Message Extension in SAML Authentication Requests](https://docs.swedenconnect.se/technical-framework/updates/18_-_User_Message_Extension_in_SAML_Authentication_Requests.html).
+> [User Message Extension in SAML Authentication Requests](https://docs.swedenconnect.se/technical-framework/latest/18_-_User_Message_Extension_in_SAML_Authentication_Requests.html).
 
 <a name="sc-dss-ext"></a>
 **\[SC.DSS.Ext\]**
@@ -603,7 +603,7 @@ Object Identifier Registry for Sweden Connect<sup>*</sup>
 
 <a name="id-binding"></a>
 **\[ID-Binding\]**
-> [Binding eIDAS Identities to Records in the Swedish Population Register](https://docs.swedenconnect.se/technical-framework/Identity_Binding.html)
+> [Binding eIDAS Identities to Records in the Swedish Population Register](https://docs.swedenconnect.se/technical-framework/Identity_Binding.html)
 
 <a name="svt-pdf"></a>
 **\[SVT-PDF\]**
@@ -638,7 +638,7 @@ Object Identifier Registry for Sweden Connect<sup>*</sup>
 
 - Section, 3.1.3.5, "General Entity Categories", was introduced and `http://id.swedenconnect.se/general-ec/1.0/secure-authenticator-binding` and `http://id.swedenconnect.se/general-ec/1.0/accepts-coordination-number` was added.
 
-- In section 3.2, an object identifier (OID) for Signature Validation Token extension was added and one OID for a SVT timestamp policy.
+- In section 3.2, an object identifier (OID) for Signature Validation Token extension was added and one OID for an SVT timestamp policy.
 
 - Added service entity categories `http://id.swedenconnect.se/ec/1.0/loa3-orgid` and `http://id.swedenconnect.se/ec/1.0/loa3-name` to section 3.1.3.1.