Document ID: chunk:federal_register_of_legislation:F2024L01443:body:0:p46
Version: federal_register_of_legislation:F2024L01443
Segment Type: other
Provision Reference: 
Character Range: 159999–163088

express consent to share, an error MUST be raised.

1.2.3      Access policy

 Attributes shared with PRPs via the AGDIS are either readily available to PRPs or require approval to access. The rules defining if or why a PRP can request attributes or attribute sets is referred to as an access policy in this Schedule.

 An attribute sharing policy MUST outline the access policy that applies to its attributes or attribute sets.

 An attribute sharing policy MAY extend the access policy for a given context provided the intent of the policy is not overridden.

 The 4 access policies available under this Schedule are outline in Table 3 below.

 Table 3 Access policies that MUST be applied to attributes

Policy         Details
Open           Any PRP MAY request an attribute or attribute set with this access control.

               If attributes are available, an ASP, ISP and IXP MUST fulfill requests for attributes subject to this access policy.
Not available  The attribute request MUST NOT be fulfilled.

               An ASP, ISP and IXP MAY respond with an error.
Restricted     A PRP MUST be approved to request this attribute or attribute set.

               An IXP MUST only broker requests to the ASP, ISP and IXP that are permitted to fulfill the request.
Platform       A PRP MUST meet the platform specific requirements to have the attribute request fulfilled.

               An IXP MUST only broker these attribute requests to the ASP, ISP and IXP that can fulfill the requests.

               An IXP MAY respond with an error if the PRP is not a member of the attribute's related platform or approved by the platform to request the attribute or attribute set.

1.2.4      Data representation

 An attribute sharing policy MUST be accompanied by a high-level specification of an attribute or attribute set's underlying values.

 The specification MUST outline the implementation agnostic features of the attribute or attribute set including the data type and the range of acceptable values.

 The default character encoding used for attributes being transmitted across the AGDIS is UTF-8.

 If an attribute set for a given federation protocol uses a different character encoding the data representation MUST stipulate the character encoding used.

2.        Core Attributes

 This Chapter outlines the attribute sharing policies for the Core Attributes available from the AGDIS.

2.1   Mutual attributes

 An IXP MUST support brokering attribute requests for all mutual attributes. An ISP MUST support processing attribute requests for all mutual attributes.
 The available mutual attributes supported under this profile are outlined in Table 4 below.

 Table 4 Mutal Attribute Sets

Attribute set              Attributes                                                                   Description
Core                       Full Name Family Name Given Names Middle Names Preferred Name Date of Birth  The core attributes that describe an individual – name and date of birth.
                           Core Attributes Last Updated
Validated Contact