EXAMPLE OF A COMPLETED PSN CODE TEMPLATE ANNEX B FOR CODE OF CONNECTION (COCO)
←
→
Page content transcription
If your browser does not render page correctly, please read the page content below
Example of a completed
PSN Code Template Annex B
for Code of Connection (CoCo)
This completed version of a CoCo has been anonymised for use by local authorities to aid their CoCo submission.
Items in the template that are not applicable to PSN Customers, as indicated in the 'Applies To' column, have been
marked grey to clarify that they are not required to be filled in. Note that the tab 'Technical Interoperability' does not
have any entries required by PSN Customers so printing this tab is not necessary.
GuidanceUNCLASSIFIED
PSN Code Template exemplar Website Version V1 0 Once completed, this document takes the classification of the system it describes Governance
Governance
Id Subject Obligation Compliance Priority Applies To Compliant Supporting Evidence
(Y/N/Waiver)
COM Compliance: from "PSN Compliance v3.7"
COM.1 Compliance PSN Customers, PSN Service Providers and GCN Service Providers Inspection SHALL GCNSPs Y
shall ensure that the body charged with verifying PSN Compliance shall DNSPs
be demonstrably independent of the business function applying for PSNSPs
compliance, impartial and professionally competent in the disciplines Customers
covered by PSN Conditions.
Independent verifiers for PSN Services and GCN Services need not be
external organisations, provided they have different board level reporting
lines to the function requesting verification. Note however that the
Accreditation of PSN Services and GCN Services is undertaken through
the PGA, and any associated IA activities are undertaken by providers
certified by CESG.
Independent verifiers for PSN Customer Environments – ie CoCo
Assessors – shall be sufficiently independent , impartial and
professionally competent such that they can make a judgement, and
specifically an IA Risk judgement, on behalf of the Infrastructure SIRO,
not the individual PSN Customer.
Independent Verifiers, including CoCo Assessors, shall be cleared to an
appropriate level, such that can access the documentation and systems
that they are verifying.
COM.2 Compliance All PSN Services and GCN Services require Accreditation. The PSNA will Inspection SHALL GCNSPs Y
require an Accreditation decision prior to awarding a PSN Compliance DNSPs
Certificate for a service. PSNSPs
PSN Customers shall accept that the PSNA will involve the PSN Customers
Accreditation Panel prior to awarding a PSN Compliance Certificate for a
customer environment.
COM.3 Compliance Whilst adherence to IA and all other Conditions will be checked through Declaration SHALL GCNSPs Y
the normal cycle of PSN Compliance follow-up visits, it is incumbent on all DNSPs
stakeholders to notify the PSNA immediately if there is a concern that any PSNSPs
Obligations are not being met. Customers
UNCLASSIFIED Page B: Gov: 2UNCLASSIFIED
PSN Code Template exemplar Website Version V1 0 Once completed, this document takes the classification of the system it describes Governance
Governance
Id Subject Obligation Compliance Priority Applies To Compliant Supporting Evidence
(Y/N/Waiver)
COM.4 Compliance Permitted traffic flows on PSN are as follows: Declaration SHALL GCNSPs N/A
DNSPs
- traffic shall flow from a PSNSP (either a Network Provider or a Service PSNSPs
Provider) to/from a DNSP but not directly to the GCN;
- traffic shall flow from a DNSP to any other DNSP via the GCN;
- traffic shall NOT flow from a DNSP to another DNSP other than via the
GCN. e.g. traffic shall not flow via a PSNSP connected to 2 DNSP‟s;
- traffic shall not flow via a private connection between 2 DNSP‟s;
- traffic shall NOT flow from a PSNSP to another PSNSP other than via a
DNSP or DNSPs and GCN(s).
COM.5 Compliance If a PSN Customer shares any non-PSN service across the PSN from its Inspection SHALL GCNSPs Y
Customer Environment, then specific IA conditions – listed in Annex B of DNSPs
the Code Template – apply. In addition to these IA conditions: PSNSPs
Customers
- the service shall not be advertised as PSN Compliant or a PSN Service;
- The PSN Customer shall access the non-PSN service via a PSN
Compliant connection service
- The non-PSN Service shall only be visible to the other PSN Customers
authorised to use the service and shall not be generally visible or
advertised
- the number of PSN Customers sharing the service (in addition to the
PSN Customer providing the service), shall be TEN or less.
- the total number of users sharing the service (in addition to those of the
PSN Customer providing the service), shall be ONE THOUSAND or less.
COM.6 Compliance Where PSN Customers, PSN Consumers or PSN Service Providers Test SHALL GCNSPs Y Member of a PSN Accredited
come together to form a PSN Aggregated Network: DNSPs Aggregated Gateway
PSNSPs
- all the individual networks shall all be at the same Impact Level; Customers
- all the individual networks shall have the same (or very similar) risk
profile;
- all the individual networks shall use shared onward connections;
- the aggregated network shall have a single entity representing it.
UNCLASSIFIED Page B: Gov: 3UNCLASSIFIED
PSN Code Template exemplar Website Version V1 0 Once completed, this document takes the classification of the system it describes Governance
Governance
Id Subject Obligation Compliance Priority Applies To Compliant Supporting Evidence
(Y/N/Waiver)
COM.7 Compliance Where a PSN Customer is using a PSN network to provide a private Test SHALL GCNSPs Y
WAN, then security gateways (e.g. firewalls) at each end point DNSPs
(customer site or network) on the WAN are not required to achieve PSN PSNSPs
Compliance, provided: Customers
- the PSN Customer has signed the Code of Connection with the
context of multiple sites included;
- there shall be no connectivity between networks of different protective
markings or risk profiles at the end points other than via accredited
interoperability gateways;
- there shall be no onward connections from the end locations other
than by assured border gateways.
COM.8 Compliance PSN Customers, PSN Service Providers and GCN Service Providers Declaration SHALL GCNSPs Y
shall recognise that the PSN Authority is the only organisation able to DNSPs
issue and rescind PSN Compliance Certificates, or change any PSNSPs
requirements or Conditions of PSN Compliance. Customers
COM.9 Compliance The wording that shall be used in PSN Supply Agreements is provided in Inspection SHALL DNSPs Y
Annex A of the PSN Code Template. PSNSPs
Customers
Moving to a new version of the PSN Code Template will require PSN
Supply Agreements to change. PSN Supply Agreements shall allow for
changes to the Compliance Conditions via formal change control (see
PSN Document Management and Change Control).
The Applicant need not necessarily comply with the obligations stated in
the latest approved version of the Code Template immediately. The
Applicant shall adopt the latest version of the Code Template in
accordance with the degree of urgency set out for each change, provided
by the PSN Authority, which may be:
- changes that need to be applied at some convenient point in the future,
with the caveat that there may be consequences to not applying them;
- changes that need to be applied within a certain timescale;
- changes that need to be applied with some urgency.
The PSNA shall work with PSN and GCN Service Providers, PSN
Customers and other stakeholders through the PSN governing bodies to
understand and manage the impact of changes to the PSN Operating
Model, however the final approval for any change will be the PSNA.
UNCLASSIFIED Page B: Gov: 4UNCLASSIFIED
PSN Code Template exemplar Website Version V1 0 Once completed, this document takes the classification of the system it describes Governance
Governance
Id Subject Obligation Compliance Priority Applies To Compliant Supporting Evidence
(Y/N/Waiver)
COM.10 Compliance PSN Compliance status shall be referenced in PSN Supply Agreements Inspection SHALL GCNSPs Y
and flowed down to individual agreements between Service Providers, DNSPs
where those Service Providers are providing PSN or GCN services. PSNSPs
Customers
COM.11 Compliance The Applicant shall manage and is accountable for the scheduling and Declaration SHALL GCNSPs N/A
cost of compliance for their service(s) or environments, including but not DNSPs
limited to the costs of any third party independent assurance and testing PSNSPs
bodies, or PSN Authority resources. The Applicant shall accept that
compliance requests may be subject to rescheduling by the PSN
Authority, according to the PSNA‟s prioritisation criteria.
Any costs will be agreed between the PSNA and the Applicant prior to
the costs being incurred.
COM.12 Compliance The prospective PSN Service Provider shall complete and submit a code Inspection SHALL GCNSPs N/A
(including signatures and annexes) for the candidate service to signal DNSPs
their intent to the PSNA to begin the compliance on-boarding process. PSNSPs
COM.13 Compliance To signal their intent to the PSNA to begin the compliance on-boarding Inspection SHALL Customers Y
process, the prospective PSN Customer shall submit a completed code to
the PSNA, or if the Customer is already GCSX CoCo 3.2 or 4.1 compliant
then they shall submit evidence of this compliance to the PSNA.
COM.14 Compliance PSN Customers accept that the decision on whether a detailed IA review Declaration SHALL Customers Y
is required is based the degree of IA risk associated with the PSN
Customer and the services it is consuming, and random sampling.
UNCLASSIFIED Page B: Gov: 5UNCLASSIFIED
PSN Code Template exemplar Website Version V1 0 Once completed, this document takes the classification of the system it describes Governance
Governance
Id Subject Obligation Compliance Priority Applies To Compliant Supporting Evidence
(Y/N/Waiver)
COM.15 Compliance The Applicant shall accept that the PSNA applies the following guidelines Declaration SHALL GCNSPs N/A
for the prioritisation of compliance applications and submissions for DNSPs
services: PSNSPs
- will in general be scheduled on a first in first out basis;
- may, at the determination of the PSN Operations Director, be
prioritised where: a contract signing, contract extension or contract
deliverable is relying on a particular service achieving PSN compliance
[here, “contract” applies to a single contract or a framework], and,
- may, at the determination of the PSN Operations Director, be
prioritised where there is wider benefit to the UK Public Sector.
The Applicant shall also accept that whilst the PSNA will endeavour to
take into account the urgency of applications in accordance with the
criteria set out above, Service Providers and Customers must always
submit any applications in good time, assuming that it will be dealt with on
a first in first out basis, and must note that any decisions regarding
prioritisation will be at the discretion of the PSNA. Further, the PSNA will
not prioritise one application over another where this would give an undue
advantage to one supplier, where, for example two or more applicants are
bidding for the same contract or where the applications relate to similar
products which may compete with each other.
COM.16 Compliance The Applicant shall accept that a PSN Compliance Certificate is awarded Inspection SHALL Customers Y
prior to a Customer Environment being connected to the PSN or used to
receive PSN Services.
COM.17 Compliance A change to a PSN Service or a Customer Environment that affects a Declaration SHALL GCNSPs Y
Code shall be captured in the Code. A changed Code shall have been re- DNSPs
signed and resubmitted by the anniversary of date when the original Code PSNSPs
was signed. Customers
A change to a GCN Service shall undergo Compliance Verification as
described in Schedule 4 of the DoU.
COM.18 Compliance To update a PSN Service, the PSN Service Provider shall update its Inspection SHALL DNSPs N/A
Code, and resubmit it to the PSN Authority. The PSN Service Provider PSNSPs
shall work with third party independent assurance and testing bodies (as
appointed by or approved by the PSN Authority) and the PGA to confirm
whether or not the change impacts the certification of its existing PSN
Services, and inform the PSN Authority if this is the case. If necessary,
the PSN Authority shall update the PSN Compliance Certificate.
UNCLASSIFIED Page B: Gov: 6UNCLASSIFIED
PSN Code Template exemplar Website Version V1 0 Once completed, this document takes the classification of the system it describes Governance
Governance
Id Subject Obligation Compliance Priority Applies To Compliant Supporting Evidence
(Y/N/Waiver)
COM.19 Compliance To update a Customer Environment, a PSN Customer shall update its Inspection SHALL Customers Y
Code, and resubmit it to the PSN Authority. The PSN Customer shall
work with third party independent assurance and testing bodies (as
appointed by or approved by the PSN Authority) to confirm whether or not
the change impacts the certification of its existing Customer
Environments, and inform the PSN Authority if this is the case. If
necessary, the PSN Authority shall update the affected PSN Compliance
Certificate.
COM.20 Compliance To remove an individual PSN Service or Customer Environment, a PSN Declaration SHALL DNSPs Y
Service Provider or PSN Customer (as applicable) shall notify the PSN PSNSPs
Authority. The PSN Authority shall rescind the appropriate PSN Customers
Compliance Certificate.
COM.21 Compliance To exit from the marketplace, the PSN Service Provider or PSN Customer Declaration SHALL DNSPs Y
shall give six months‟ written notice to the PSN Authority, and the PSN PSNSPs
Authority shall rescind all applicable PSN Compliance Certificates. Customers
COM.22 Compliance The recipient of a Compliance Warning Notice shall provide its response, Declaration SHALL DNSPs Y
containing timescales that are acceptable to the PSNA, within Ten (10) PSNSPs
Working Days of receiving the Compliance Warning Notice. Customers
COM.23 Compliance Following instruction from the Infrastructure SIRO to rescind a PSN Declaration SHALL DNSPs Y
Compliance Certificate, the PSNA will require the affected Service or PSNSPs
Customer Environment – and if necessary any connected PSN Services Customers
and Customer Environments – to disconnect from the PSN. PSN
Customers and Service Providers shall follow any such instruction in the
timeframe required by the PSNA.
COM.24 Compliance PSN Service Providers, GCN Service Providers and PSN Customers Inspection SHALL GCNSPs Y
shall ensure that there are clauses in their contracts, as specified in DNSPs
Annex A of the PSN Code Template to cater for the scenario where a PSNSPs
PSN Compliance Certificate is rescinded. Customers
COM.26 Compliance The Applicant shall ensure that their PSN Compliance test results are Inspection SHALL DNSPs Y
independently verified, using either PSN Authority resources, or third PSNSPs
party independent assurance and testing bodies as appointed by or Customers
approved by the PSN Authority, as a condition for achieving PSN
Compliance Certification. The Applicant shall ensure that any
independent third party conducting these tests acknowledges in writing
that the tests results are to be provided to the PSN Authority and that the
PSN Authority will be relying on those results. The Applicant shall make
these test results available to the PSN Authority on request and as
required.
UNCLASSIFIED Page B: Gov: 7UNCLASSIFIED
PSN Code Template exemplar Website Version V1 0 Once completed, this document takes the classification of the system it describes Governance
Governance
Id Subject Obligation Compliance Priority Applies To Compliant Supporting Evidence
(Y/N/Waiver)
COM.27 Compliance Where the PSN Authority has reasonable and just cause to intervene in a Declaration SHALL DNSPs Y
PSN Compliance Verification: (1) the Applicant shall allow reasonable PSNSPs
access to its site and personnel upon receiving not less than Twenty (20) Customers
Working Days‟ prior written notice (and shall use reasonable endeavours
to allow such access within Ten (10) Working Days thereof) (2) the
Applicant hereby gives its consent to the PSN Authority appointing
independent third party organisation(s) to conduct such PSN Compliance
Verification.
COM.28 Compliance Where Compliance Verification involves Tests, the Applicant shall Inspection SHALL DNSPs Y
prepare a test plan and test scripts for Compliance Verification. The test PSNSPs
scripts shall be detailed enough to show compliance with all Conditions. Customers
COM.29 Compliance The Applicant shall allow the PSN Authority to review any PSN Declaration SHALL DNSPs Y
Compliance test scripts and test plans prior to the conduct of Compliance PSNSPs
Verification. The PSN Authority may – but shall not be obliged to – review Customers
these.
COM.30 Compliance If the PSN Authority does choose to review the test scripts and test plans Declaration SHALL DNSPs Y
then it shall do so within Ten (10) Working Days providing written PSNSPs
comments to the Applicant. The Applicant shall submit revised test plans Customers
and test scripts to the PSN Authority for its review within Ten (10)
Working Days of receipt of such comments.
COM.31 Compliance Where the PSN Authority provides written comments to test plans and Declaration SHALL DNSPs Y
test scripts, the Applicant shall not commence Compliance Verification PSNSPs
until such comments have been addressed. Customers
COM.32 Compliance The Applicant shall allow the PSN Authority to review any PSN Declaration SHALL GCNSPs Y
Compliance test scripts, test plans and the associated results at any time DNSPs
during, on or after the completion of Compliance Verification. PSNSPs
Customers
COM.33 Compliance The Applicant and the PSN Authority shall meet to review the test plans Declaration SHALL DNSPs Y
and test scripts within Ten (10) Working Days of any written request by PSNSPs
the PSN Authority. Customers
COM.34 Compliance On completion of Compliance Verification, the Applicant shall provide a Declaration SHALL DNSPs Y
written report to the PSN Authority, prepared by an independent PSNSPs
compliance verification body, which details any compliance related Customers
issues, actions, observations and a compliance recommendation.
UNCLASSIFIED Page B: Gov: 8UNCLASSIFIED
PSN Code Template exemplar Website Version V1 0 Once completed, this document takes the classification of the system it describes Governance
Governance
Id Subject Obligation Compliance Priority Applies To Compliant Supporting Evidence
(Y/N/Waiver)
COM.35 Compliance PSN Service Providers and PSN Customers shall submit a self Inspection SHALL DNSPs Y
assessment of their Compliance status annually. This shall consist of a re- PSNSPs
submitted Code, re-signed and dated, with any changes highlighted. Customers
When resubmitting a Code, PSN Service Providers and PSN Customers
shall consider whether to involve independent verification, based on the
extent of any changes to the Code.
PSN Service Providers and PSN Customers shall accept that when
changes have been made to a Code without independent verification, the
PSNA may require a Compliance Review.
COM.36 Compliance PSN Service Providers, GCN Service Providers and PSN Customers Declaration SHALL GCNSPs Y
shall accept that a small percentage of PSN Service Providers, GCN DNSPs
Service Providers, and PSN Customers will be required by the PSN PSNSPs
Authority to undergo a compliance review in any 12 month period. Customers
COM.37 Compliance The PSN Authority will publish a compliance review schedule annually. Declaration SHALL GCNSPs Y
This schedule will list the PSN Service Providers, GCN Service Providers DNSPs
and PSN Customers that are required to undergo a compliance review PSNSPs
within an upcoming 12 month period. PSN Service Providers, GCN Customers
Service Providers and PSN Customers shall ensure that they know when
they are required to undergo a compliance review.
PSN Service Providers, GCN Service Providers and PSN Customers
accept that the decision on whether a compliance review is required is
based on a number of factors including: the length of time since the last
review, the degree of IA risk associated with the PSN Service Provider,
GCN Service Provider or PSN Customer, random sampling or whether
there are any significant changes since any previous application.
COM.38 Compliance PSN Service Providers, GCN Service Providers and PSN Customers Declaration SHALL GCNSPs Y
shall accept that the PSN Authority may choose to initiate an unscheduled DNSPs
compliance review at any time, where the PSN Authority has reasonable PSNSPs
and just cause to believe that a compliance condition is not being met. Customers
Where such a compliance review is required, PSN Service Providers,
GCN Service Providers and PSN Customers shall allow reasonable
access to its site and personnel upon receiving not less than Twenty (20)
Working Days‟ prior written notice (and shall use reasonable endeavours
to allow such access within Ten (10) Working Days thereof).
UNCLASSIFIED Page B: Gov: 9UNCLASSIFIED
PSN Code Template exemplar Website Version V1 0 Once completed, this document takes the classification of the system it describes Governance
Governance
Id Subject Obligation Compliance Priority Applies To Compliant Supporting Evidence
(Y/N/Waiver)
COM.39 Compliance a PSN Supply Agreement shall always exist where PSN Services are Declaration SHALL GCNSPs Y
being provided, whether these services are being provided: DNSPs
PSNSPs
- directly to PSN Customers; Customers
- to intermediate PSN Service Providers;
- between a PSN Service Provider and a PSN Customer within the same
organisation;
- between Public Sector organisations.
COM.40 Compliance Organisations that are both PSN Customers and PSN Service Providers Declaration SHALL GCNSPs Y
shall commit and demonstrate that their PSN Customer function is DNSPs
independent of their PSN Service Provider function, such that the PSNA PSNSPs
can govern each function independently of the other. Separate points of Customers
contact shall be provided for each function
COM.41 Compliance A DNSP network shall allow traffic with any direct connection it has with Declaration SHALL DNSPs N/A
any PSN Customer or PSN Service Provider to transit across the GCN,
subject to any access restrictions imposed by the PSN Customer or PSN
Service Provider.
COM.42 Compliance A PSN Service offering network services shall allow traffic with any direct Declaration SHALL PSNSPs N/A
connection it has with any PSN Customer or PSN Service Provider to
transit to a DNSP network, subject to any access restrictions imposed by
the PSN Customer or PSN Service Provider.
COM.43 Compliance A PSN Central Service Provider shall publish prices, terms and service Inspection SHALL GCNSPs N/A
levels for its PSN Central Service. Identical pricing, quality and levels of DNSPs
service shall be provided to all organisations able to buy the service. PSNSPs
COM.44 Compliance A PSN Central Service shall be able to be procured separately from any Inspection SHALL GCNSPs N/A
other service offered by a PSN Service Provider. Hence, procurement of DNSPs
a PSN Central Service shall not be dependent upon procurement of any PSNSPs
other service being marketed by that supplier; similarly, procurement of
any service shall not be dependent upon procurement of a PSN Central
Service.
MIR Management Information: from "Management Information Requirements v1.2"
MIR.1 Management Provide quarterly information [based on the HMG financial year] to the Inspection SHALL GCNSP N/A
Information PSNA in respect of actual GCN service pricing information. These are the
actual prices charged by the GCNSP to its DNSP customer(s) at the end
of the period in question. A pro forma response is provided in Table 1 of
Management Information Requirements.
th
The information provided shall be provided by the 15 of the month
following quarter end. If no services are being provided a null return is
required
UNCLASSIFIED Page B: Gov: 10UNCLASSIFIED
PSN Code Template exemplar Website Version V1 0 Once completed, this document takes the classification of the system it describes Governance
Governance
Id Subject Obligation Compliance Priority Applies To Compliant Supporting Evidence
(Y/N/Waiver)
MIR.2 Management Provide information periodically as detailed in the following sections to the Inspection SHALL GCNSP N/A
Information PSNA 3.4 to 3.11.
The frequency with which this information is to be provided over the first
12 months of operation is:
1. in a monthly report for quantitative information [unless it says otherwise
against the requirement in this document]
2. in a quarterly report with summary quantitative information with
supporting narrative. Quarterly summary reports shall be presented at a
Service Review Meeting. There is a Service Review Meeting for each
GCNSP and one (1) week before each meeting the GCNSP shall provide
the report to the PSNA.
Following the first 12 months the information shall be provided quarterly.
The format that the information is to be provided in is to be mutually
agreed by the PSNA and GCNSPs.
MIR.3 Management The number of GCN Service „instances‟ deployed and in live operation. Inspection SHALL GCNSP N/A
Information
MIR.4 Management The number of service Incidents raised by severity level Inspection SHALL GCNSP N/A A Remote Working Policy is in place.
MIR.5 Information
Management The number of occasions that a DNSP customer of the GCN Service was Inspection SHALL GCNSP N/A The remote/mobile working solutions that
Information not informed within 30 minutes when a service affecting Incident was
raised, or the status of an existing Incident changed.
Also as a percentage of the total number of Incidents raised
MIR.6 Management The number of service Incidents reported to the service provider but not Inspection SHALL GCNSP N/A
Information accepted or rejected (with justification), within 30 minutes for 90% of all
incidents received in any one hour during the Agreed Service Time.
Also as a percentage of the total number of Incidents raised
MIR.7 Management The number of security Incidents escalated to the PSN Security Manager. Inspection SHALL GCNSP N/A
Information
Also as a percentage of the total number of Incidents
MIR.8 Management Narrative across all Incidents explaining any trends particularly in types of Inspection SHALL GCNSP N/A
Information Incident and what is being done about them.
Frequency: quarterly
UNCLASSIFIED Page B: Gov: 11UNCLASSIFIED
PSN Code Template exemplar Website Version V1 0 Once completed, this document takes the classification of the system it describes Governance
Governance
Id Subject Obligation Compliance Priority Applies To Compliant Supporting Evidence
(Y/N/Waiver)
MIR.9 Management Narrative across all Problems detailing the number of Problems remaining Inspection SHALL GCNSP N/A
Information open, the number of Problems closed and the number of new Problems
raised, explaining any trends and what is being done about them.
Frequency: quarterly
MIR.10 Management The number of Tier 2 or Tier 3 Changes raised and for which the service Inspection SHALL GCNSP N/A
Information provider has been identified as the Change Owner
MIR.11 Management The number of Emergency Changes which the service provider has had Inspection SHALL GCNSP N/A
Information to implement for its GCN service, and as a percentage of the total number
of Changes raised against that service
MIR.12 Management The number of failed Changes implemented by the service provider on its Inspection SHALL GCNSP N/A
Information GCN Service, and as a percentage of the total number of Changes raised
against that service.
Failed Changes are those which go wrong and affect service, not those
which are reversed or backed out before serious disruption occurs.
MIR.13 Management The number of occasions that an impact statement in response to a Inspection SHALL GCNSP N/A
Information Request for Change was not submitted to the DNSP customer within ten
(10) Working Days or the agreed extension period.
Also as a percentage of the total number of Changes being assessed by
the service provider
MIR.14 Management Narrative across all Changes explaining any trends and a section Inspection SHALL GCNSP N/A
Information explaining forthcoming planned service affecting work for the following 12
months that has not yet been submitted for Change approval.
Frequency: quarterly
MIR.15 Management The number of occasions that a Service Desk function was not available Inspection SHALL GCNSP N/A
Information to manage Incidents during service hours.
MIR.16 Management The number of occasions that the PSN GCN has been unavailable due to Inspection SHALL GCNSP N/A
Information scheduled and unscheduled maintenance activities and the effective %
availability outage calculated as the:
total time in a period – total time unavailable in a period / total time in a
period
all in seconds.
MIR.17 Management The number of occasions that the DNSP customer was not notified of a Inspection SHALL GCNSP N/A
Information Significant Event within 30 minutes of the Event occurring.
MIR.18 Management The number of Events that have a security impact on the PSN, and as a Inspection SHALL GCNSP N/A
Information percentage of all Events detected for that GCN Service
UNCLASSIFIED Page B: Gov: 12UNCLASSIFIED
PSN Code Template exemplar Website Version V1 0 Once completed, this document takes the classification of the system it describes Governance
Governance
Id Subject Obligation Compliance Priority Applies To Compliant Supporting Evidence
(Y/N/Waiver)
MIR.19 Management Narrative across all Events explaining any trends and what is being done Inspection SHALL GCNSP N/A
Information about them.
Frequency: quarterly
MIR.20 Management Narrative regarding Security Incidents and trends regarding types of Inspection SHALL GCNSP N/A
Information Incident e.g. attacks on network, logon, device failures etc.
Frequency: quarterly
MIR.21 Management A list of service improvement initiatives for the GCN Services, current and Inspection SHALL GCNSP N/A
Information planned with narrative explaining intended outcome and achievement of
progress towards this.
Narrative of service improvement initiatives implemented over the past 12
months and the outcomes achieved.
Frequency: quarterly
MIR.22 Management Provide recommendations for service improvements in respect of their Inspection SHALL GCNSP N/A
Information own services or the GCN as a whole, including „lessons learned‟, to the
PSNA on a quarterly basis, as part of the report prior to the Service
Review Meeting. If there are no service improvements to be suggested
then a null return is required
MIR.23 Management Provide the PSNA with a brief assessment of the cost and time taken to Inspection SHALL GCNSP N/A
Information achieve GCN Compliance Certification and of being awarded and
maintaining this at the conclusion of each Compliance Verification
exercise (set-up, periodic or exceptional) within thirty (30) Working Days
of the conclusion of the Compliance Verification exercise, and shall
review with the PSNA at the next Service Review Meeting.
UNCLASSIFIED Page B: Gov: 13UNCLASSIFIED
PSN Code Template exemplar Website Version V1 0 Once completed, this document takes the classification of the system it describes Technical Interoperability
Technical Interoperability - Customers do not have to fill in anything on this sheet
Id Subject Obligation Compliance Priority Applies To Compliant Supporting Evidence
(Y/N/Waiver)
AVA Availability: from "PSN Technical Domain Description v2.3"
AVA.1 Availability The PSN as a whole must have the capability to provide for Declaration of SHALL DNSP,
99.999% services availability for a given service instance, whereby compliance. GCNSP
the capability to provide for a 99.999% services availability solution
may be delivered over one or more PSN service providers.
AVA.2 Availability Each GCNSPs‟ PoC must achieve a minimum service availability of Declaration of SHALL GCNSP
99.95%. compliance.
AVA.3 Availability The DNSP as a component service slice must provide a minimum Declaration of SHALL DNSP
service availability of 99.98%. compliance.
TIM Network Timing: from "PSN Technical Domain Description v2.3"
TIM.1 Network Timing All PSN provider networks must synchronize Network Declaration of SHALL DNSP,
infrastructure timing from a common Stratum 0 clock source compliance. GCNSP
such as Global Positioning Systems (GPS).
TIM.2 Network Timing Network Infrastructure timing must be disseminated to all Declaration of SHALL DNSP,
PSN networking infrastructure using industry standard compliance. GCNSP
methods such as the Network Time Protocol (NTP).
TIM.3 Network Timing All GCNSP MPLS and routing Infrastructure elements are to Declaration of SHALL GCNSP
be aligned to UTC (time of day) to within (+-) “10” ms for 99% compliance.
of measurement instances per month for PSNA and GCNGB
agreed measurements methods. Initial compliance evidence
is to be provided via suitable compliance statements from
each prospective GCNSP
MON PSN Network Monitoring Obligations: from "PSN Technical Domain Description v2.3"
MON.1 Network PSN technical requirements and standards that apply to GCN Declaration of SHALL DNSP,
Monitoring and DNSP Monitoring are specified in the PSN Service compliance. GCNSP
Management Framework available on the Cabinet Office
website at the following location:
http://www.cabinetoffice.gov.uk/content/public-services-
network
NNI Network to Network Interface: from "PSN Technical Domain Description v2.3"
NNI.1 Network to All service providers must adhere to the technical standards, Declaration of SHALL DNSP,
Network deployment methodologies and best practice compliance. GCNSP
Interface recommendations as detailed in the Technical Domain
Description.
NNI.2 Network to All devices forming part of the NNI interconnect will be Declaration of SHALL DNSP,
Network housed at the respective service provider premises. compliance. GCNSP
Interface
NNI.3 Network to Service provider facilities will be physically secured with Declaration of SHALL DNSP,
Network access only being granted to approved and suitably screened compliance. GCNSP
Interface staff.
UNCLASSIFIED Page B: Tech: 14UNCLASSIFIED
PSN Code Template exemplar Website Version V1 0 Once completed, this document takes the classification of the system it describes Technical Interoperability
Technical Interoperability - Customers do not have to fill in anything on this sheet
Id Subject Obligation Compliance Priority Applies To Compliant Supporting Evidence
(Y/N/Waiver)
NNI.4 Network to In all cases, the GCN service provider control the entire Declaration of SHALL DNSP,
Network infrastructure to actual cable/fibre or patch-panel hand-off at compliance. GCNSP
Interface the DNSP or third-party GCNSP location.
NNI.5 Network to The GCNSP will provision all cabling to the associated Declaration of SHOULD GCNSP
Network termination point. From this point, cabling is expected to be compliance.
Interface provided via direct patching between peers in a point-to-point
fashion. This would not require any further devices, such as
switches, to be placed in-line between connections.
NNI.6 Network to The service provider will ensure adequate labelling of all NNI Declaration of SHALL DNSP,
Network devices to current standards so that equipment may be easily compliance. GCNSP
Interface identifiable in the event of any issues.
NNI.7 Network to All NNI interconnects will employ monitoring mechanisms to Declaration of SHALL DNSP,
Network ensure that any link failure is reported in a timely fashion. compliance. GCNSP
Interface This failure will be immediately reported into the relevant
management platform with an associated alert condition.
NNI.8 Network to VLANs will be allocated from the existing GCNSP and DNSP Declaration of SHALL DNSP,
Network provider pool. compliance. GCNSP
Interface
NNI.9 Network to In all case the service provider is expected to provision NNI Declaration of SHALL DNSP,
Network interconnects using point-to-point /30 IP addressing compliance. GCNSP
Interface presented on physical or logical sub-interfaces.
NNI.10 Network to Physical or sub-interfaces will be used for peering in all Declaration of SHALL DNSP,
Network cases. compliance. GCNSP
Interface
NNI.11 Network to Service providers will only use public AS numbers assigned Declaration of SHALL DNSP,
Network from their own allocations. compliance. GCNSP
Interface
NNI.12 Network to Any AS path manipulation (such as AS-Override, SoO and Declaration of SHALL DNSP,
Network AS prepend values) is expected to be performed at the edge compliance. GCNSP
Interface of the network via the client facing DNSP PE device. No other
manipulation of the AS Path is expected.
NNI.13 Network to All service providers should provide a statement of current Declaration of SHALL DNSP,
Network AS 32Bit capability as well as a roadmap to deliver this compliance. GCNSP
Interface capability.
NNI.14 Network to All service providers support the standard BGP timers. Any Declaration of SHALL DNSP,
Network enhancement to these values will be agreed between parties compliance. GCNSP
Interface for use at the NNI.
NNI.15 Network to Where agreed by both parties the service provider will Declaration of SHALL DNSP,
Network provide authentication of the BGP session at the NNI. compliance. GCNSP
Interface
UNCLASSIFIED Page B: Tech: 15UNCLASSIFIED
PSN Code Template exemplar Website Version V1 0 Once completed, this document takes the classification of the system it describes Technical Interoperability
Technical Interoperability - Customers do not have to fill in anything on this sheet
Id Subject Obligation Compliance Priority
Applies To Compliant Supporting Evidence
(Y/N/Waiver)
NNI.16 Network to All service providers should apply maximum values to the Declaration of SHOULD DNSP,
Network allowed BGP prefix count. However, any such value will be compliance. GCNSP
Interface scaled based on government demand without enforcing any
limitation on the consumer.
NNI.17 Network to All service providers will support community values at the NNI Declaration of SHALL DNSP,
Network point. compliance. GCNSP
Interface
NNI.18 Network to The service provider commits to applying the correct filters to Declaration of SHALL DNSP,
Network limit communication to the required VPN resource only. For compliance. GCNSP
Interface example, PE devices will allow direct ICMP and BGP peering
traffic only.
NNI.19 Network to All service providers will support BGP load balancing Declaration of SHALL DNSP,
Network mechanisms at the NNI interconnect (MED, BGP-Multipath compliance. GCNSP
Interface and AS prepend etc.)
NNI.20 Network to All service providers must provide a mechanism for the easy Declaration of SHALL DNSP,
Network identification and isolation of the required NNI elements compliance. GCNSP
Interface across parties in all cases to support co-operation of any
troubleshooting activities.The following parameters will be
allocated using the current OSS processes available to the
GCN service provider:
- VPN Name
- VPN Description
- VPN Route Distinguisher (RD)
- VPN Route Target (RT)
NNI.21 Network to In the event that duplicate RT values are present at the Declaration of SHALL GCNSP
Network ingress into the GCN (as provided by DNSP or customer compliance.
Interface networks) the GCN service provider must support RT re-write
functionality. This is also required if agreement cannot be
reached in the provisioning of RT values at the Inter-AS
option B interconnect.
NNI.22 Network to In the event that duplicate RD values are present at the Declaration of SHALL GCNSP
Network ingress into the GCN (as provided by DNSP or customer compliance.
Interface networks) the GCN service provider must support RD re-write
functionality.
NNI.23 Network to In the event that the service provider is required to migrate Declaration of SHALL DNSP,
Network between Option A and B deployments, it is agreed that this compliance. GCNSP
Interface operation will form part of an agreed migration strategy
without impact on the overall service.
UNCLASSIFIED Page B: Tech: 16UNCLASSIFIED
PSN Code Template exemplar Website Version V1 0 Once completed, this document takes the classification of the system it describes Technical Interoperability
Technical Interoperability - Customers do not have to fill in anything on this sheet
Id Subject Obligation Compliance Priority Applies To Compliant Supporting Evidence
(Y/N/Waiver)
NNI.24 Network to All service providers will apply suitable mechanisms to Declaration of SHALL DNSP,
Network ensure that PSN components are adequately dimensioned to compliance. GCNSP
Interface support the expected (current and forecast) levels of traffic.
NNI.25 Network to The service provider will implement the appropriate controls Declaration of SHALL DNSP,
Network and best practice methodologies required to mitigate against compliance. GCNSP
Interface attack at the NNI point.
NNI QoS and Performance: from "PSN Technical Domain Description v2.3"
QOS.1 QoS and All service providers must adhere to the technical standards, Declaration of SHALL DNSP,
Performance deployment methodologies and best practice compliance. GCNSP
recommendations as detailed in the Technical Domain
Description.
QOS.2 QoS and All GCNSP‟s, DNSP‟s and SP‟s providing packet transport Declaration of SHALL DNSP,
Performance services using MPLS Shall align their QoS service class compliance. GCNSP
policies consistent with the PSN 6 service class QoS model
throughout the Diffserv region. For GCNSPs the requirement
is to provide a fixed six service classes whilst DNSP‟s and
PSN SP‟s may have more or less service classes but must
demonstrate how they map to the PSN 6 classes consistent
with consumer traffic type requirements
QOS.3 QoS and All service providers will use common set of service class Declaration of SHALL DNSP,
Performance names across the PSN Diffserv region to provide end to end compliance. GCNSP
service class assurance.
QOS.4 QoS and Each DNSP Network must comply with the QoS performance Declaration of SHALL DNSP,
Performance metric upper bounds as detailed in the Technical Domain compliance. GCNSP
Description.
QOS.5 QoS and All DNSP‟s and SP‟s providing packet transport services Declaration of SHALL DNSP,
Performance using MPLS Shall align their respective QoS policy DSCP/ compliance. GCNSP
EXP markings to the PSN QoS model at the DNSP edge
node connected to the PoC NNI. The GCNSP will provide the
respective PSN QoS marking alignment scheme as part of
the respective peering policy.
QOS.6 QoS and Each directly connected GCNSP will mutually agree as part Declaration of SHALL DNSP,
Performance of the PoI NNI/ peering agreement as to which GCNSP‟s PoI compliance. GCNSP
interface will perform the marking alignment to the PSN QoS
model.
QOS.7 QoS and The PSN Diffserv region will also support the Class Selector Declaration of SHALL DNSP,
Performance (CS) PHB in line with the stipulations outlined in RFC 4594. compliance. GCNSP
UNCLASSIFIED Page B: Tech: 17UNCLASSIFIED
PSN Code Template exemplar Website Version V1 0 Once completed, this document takes the classification of the system it describes Technical Interoperability
Technical Interoperability - Customers do not have to fill in anything on this sheet
Id Subject Obligation Compliance Priority
Applies To Compliant Supporting Evidence
(Y/N/Waiver)
QOS.8 QoS and To mitigate the requirement to provide per VPN QoS Declaration of SHOULD DNSP,
Performance measurement and reporting on a GCN NNI, it is compliance. GCNSP
recommended that GCNSPs and DNSPs apply the NNI QoS
policy to the NNI physical bearer or aggregate logical port
QOS.9 QoS and For all DNSP‟s and SP‟s providing packet transport services Declaration of SHALL DNSP, SP
Performance using MPLS the PSN Diffserv edge node shall be capable of compliance.
providing the following minimum set of QoS capabilities over
the PSN access circuit and logical connections:
- Support for multiple logical connections on same access
circuit.
- Allocate dedicated bandwidth to logical connections on
same access circuit.
- Allocate minimum bandwidth guarantees to individual PSN
service classes within each logical connection.
- Support for performance metric differentiation between the
PSN Real-Time service class, PSN application classes
(Application Class 1-4) and PSN default service class.
- Capability to distribute unallocated bandwidth to PSN
service classes over and above the service minimum
guarantees.
- For Clarification: this statement is intended to stipulate a
requirement to support the capability as described in the
bullet points should a consumer request QoS capabilities on
their access links. It does not state it must be implemented on
the tail for all consumer sites as a matter of course.
UNCLASSIFIED Page B: Tech: 18UNCLASSIFIED
PSN Code Template exemplar Website Version V1 0 Once completed, this document takes the classification of the system it describes Technical Interoperability
Technical Interoperability - Customers do not have to fill in anything on this sheet
Id Subject Obligation Compliance Priority Applies To Compliant Supporting Evidence
(Y/N/Waiver)
QOS.10 QoS and To enable end-to-end out-of-contract and in-contract service Declaration of SHALL DNSP,
Performance continuity, all PSN service providers must comply with the compliance. GCNSP
following requirements for the PSN application classes (AF
classes):
- All DNSPs and GCNSPs must accept all three drop
precedence Diffserv codepoints on the PoC and PoI NNIs in
line with section 6.3.1.2
- All DNSPs and GCNSPs must not reclassify any PSN
application class to the PSN default service class.
QOS.11 QoS and The PSN standard for inter-provider QoS performance Declaration of SHALL DNSP,
Performance measurement and monitoring is Active Probing. Active compliance. GCNSP
probing uses custom synthetic traffic test streams or “probes”;
that are sent between active probing devices.
The active probing solution must not impact PSN consumer
traffic, either through excessive link load from measurement
probes or as the result of load placed on infrastructure by the
measurement processes such as generating and responding
to probes.
QOS.12 QoS and The service provider will support IETF „IP Performance Declaration of SHALL GCNSP
Performance Metrics (IPPM)‟ Two-Way Active Measurement Protocol compliance.
„TWAMP‟ as the QoS performance measurement protocol
standard for PSN.
Clarification: The statement has been confirmed for GCNSPs
but is not mandated for DNSPs or PSN SP(s) providing
connectivity beyond the DNSP side of the DNSP – GCNSP
NNI. The intention is not to mandate through a DNSP or PSN
SP Diffserv Domain but it does apply on the DNSP side of
the NNI.
QOS.13 QoS and The measurement of PSN QoS performance metrics is two- Declaration of SHALL DNSP,
Performance way to enable reliable metrics in an easy to deploy manner. compliance. GCNSP
Analysis of asymmetric routing and/ or queuing as well as
applications dependent on unidirectional network
performance e.g. voice/video will be performed in a on-
demand fashion as necessary.
UNCLASSIFIED Page B: Tech: 19UNCLASSIFIED
PSN Code Template exemplar Website Version V1 0 Once completed, this document takes the classification of the system it describes Technical Interoperability
Technical Interoperability - Customers do not have to fill in anything on this sheet
Id Subject Obligation Compliance Priority Applies To Compliant Supporting Evidence
(Y/N/Waiver)
QOS.14 QoS and At a minimum, all PSN service providers must provide the Declaration of SHALL DNSP,
Performance technical capability to report the following QoS performance compliance. GCNSP
metrics across the PSN Diffserv region for EF, AF1 and BE
service classes:
GCN:
- IP Round Trip Delay
- Two -Way IP Packet Loss Ratio
- One-Way IP Delay Variation in each direction.
DNSP:
- IP Round Trip Delay
- Two -Way IP Packet Loss Ratio
- One-Way IP Delay Variation for EF Class Only
QOS.15 QoS and All DNSP‟s and SP‟s providing packet transport services Declaration of SHALL DNSP, SP
Performance using MPLS Shall ensure MPLS and routing Infrastructure compliance.
elements are aligned to UTC (time of day) to within (+/-)10
ms for 99% of measurement instances per month for PSNA
agreed measurements methods. Initial compliance evidence
is to be provided via suitable compliance statements from
each prospective DNSP and SP.
Where a probe infrastructure is provided it shall be
synchronised to (+/-) 5ms from UTC time of day.
QOS.16 QoS and All MPLS and routing Infrastructure elements are to be Declaration of SHALL DNSP,
Performance aligned to UTC (time of day) to within (+-) “10” ms for 99% of compliance. GCNSP
measurement instances per month for PSNA and GCNGB
agreed measurements methods. Initial compliance evidence
is to be provided via suitable compliance statements from
each prospective GCNSP
All GCNSP probe infrastructure must be synchronised to (+-)
4ms from UTC time of day.
QOS.17 QoS and The measurement interval should be initiated randomly every Declaration of SHOULD DNSP, SP
Performance 15 minutes and consist of 200 packets for each of the test compliance.
PSN classes in the network. The results will provide an
average Two-Way Latency, average Jitter and % Packet Loss
for each test run.
UNCLASSIFIED Page B: Tech: 20UNCLASSIFIED
PSN Code Template exemplar Website Version V1 0 Once completed, this document takes the classification of the system it describes Technical Interoperability
Technical Interoperability - Customers do not have to fill in anything on this sheet
Id Subject Obligation Compliance Priority
Applies To Compliant Supporting Evidence
(Y/N/Waiver)
QOS.18 QoS and The PSN QoS model recommends the use of Poisson Declaration of SHOULD DNSP,
Performance sampling for the PSN Application and Default service classes compliance. GCNSP
and periodic sampling for the PSN Real-Time service class.
QOS.19 QoS and Packet sizes appropriate to the class of service must be shall Declaration of SHALL DNSP,
Performance for all classes of service. The PSN Real-Time service class compliance. GCNSP
must use a payload of 60 bytes to simulate the G.729 VoIP
codec. All other PSN service class probes shall be based on
400 byte IP datagrams.
QOS.20 QoS and Each GCNSP provider must comply with the following Declaration of SHALL GCNSP
Performance requirements for delivery of the active probing solution: compliance.
- All GCNSPs must provide active probing functionality on all
their respective PoC NNIs at each of their PoC locations.
- All GCNSPs must ensure all other GCNSPs can probe their
respective PSN NNI probes.
- All GCNSPs must ensure that active probing test streams
transit their respective IP infrastructure connected to the PoC/
PoI NNI e.g. ASBR(PE).
- Each GCNSP must measure and report on the minimum
set of PSN QoS performance metrics across the GCN
including GCN to DNSP NNI, per PSN service class.
QOS.21 QoS and Each DNSP‟s and SP‟s providing packet transport services Declaration of SHALL DNSP,SP
Performance using MPLS shall comply with the following requirements for compliance.
delivery of the active probing solution:
- Shall support the capability to measure and report on PSN
QoS performance metrics from their PSN Diffserv domain
edge i.e. the DNSP/SP edge node to their respective GCN
PoC NNIs.
- Shall ensure that active probing test streams transit their
respective IP infrastructure connected to the PoC NNI(s) e.g.
ASBR(PE)
QOS.22 QoS and DELETED OBLIGATION
Performance
UNCLASSIFIED Page B: Tech: 21UNCLASSIFIED
PSN Code Template exemplar Website Version V1 0 Once completed, this document takes the classification of the system it describes Technical Interoperability
Technical Interoperability - Customers do not have to fill in anything on this sheet
Id Subject Obligation Compliance Priority Applies To Compliant Supporting Evidence
(Y/N/Waiver)
QOS.23 QoS and Where a DNSP measurement or reporting standard differs Declaration of SHALL DNSP
Performance from those specified in this document, the DNSP is compliance.
responsible for appropriate concatenation of reports for PSN
consumers.
QOS.24 QoS and Each service provider must provide QoS performance Declaration of SHALL DNSP,
Performance management information to the respective PSN authorities as compliance. GCNSP
defined in the Service Management Framework and PSNA/
GB agreements. The respective QoS management
information must be made available to the PSN authorities
upon request. The frequency and format of the QoS
performance management information will be defined as part
of the overall Service Management Framework. Real time
reporting and associated data will be subject to similar
definition as part of the Service Management Framework.
QOS.25 QoS and The service provider must conform to the minimum Declaration of SHALL DNSP,
Performance performance metrics and capabilities as specified in the compliance. GCNSP
Technical Domain Description.
IP IP Addressing: from "PSN Technical Domain Description v2.3"
IP.1 IP Addressing Service providers are required to use Public IP addressing Solution Design and SHALL GCNSP,
from their own address spaces when provisioning GCN, Demonstration. DNSP
DNSP and NNI connections with neighbouring service
providers and consumer WAN devices.
The Service Provider(s) are required to provide addressing
for the following PSN entities:
- GCN to GCN
- GCN to DNSP
- GCN and DNSP to Internet
- DNSP to Consumer CE WAN port
IP.2 IP Addressing PSN services must use approved, registered IP address Solution Design and SHALL GCNSP,
ranges as detailed in the Technical Domain Description IP Demonstration. DNSP,
Address Request Process. PSNSP
IP.3 IP Addressing The service provider commits to requesting separate PSN IP Solution Design and SHALL GCNSP,
Address ranges for any RAS services. Demonstration. DNSP,
PSNSP
UNCLASSIFIED Page B: Tech: 22UNCLASSIFIED
PSN Code Template exemplar Website Version V1 0 Once completed, this document takes the classification of the system it describes Technical Interoperability
Technical Interoperability - Customers do not have to fill in anything on this sheet
Id Subject Obligation Compliance Priority Applies To Compliant Supporting Evidence
(Y/N/Waiver)
IP.4 IP Addressing The service provider commits to requesting separate PSN IP Solution Design and SHALL GCNSP,
Address ranges for any cryptographic services. Demonstration. DNSP,
PSNSP
IP.5 IP Addressing The PSN Public Address space must not be propagated Solution Design and SHALL GCNSP,
outside of government or be presented as a viable route Demonstration. DNSP,
reachable from the internet. PSNSP
IP.6 IP Addressing All entities managing IP addresses from the PSN Public Solution Design and SHALL GCNSP,
address range will be required to provide usage reports to the Demonstration. DNSP,
PSNA on a quarterly basis. These reports should include the PSNSP
following details:
- Allocation
- Usage percentage
- Usage mechanism – DHCP, RAS, Cryptographic etc.
IP.7 IP Addressing In the event that any IP range is configured incorrectly, the Solution Design and SHALL GCNSP,
service provider or submitter will be responsible for both Demonstration. DNSP,
reporting (to the PSNA) and rectifying any problems. In the PSNSP
event the service provider or submitter is unable to resolve
the issue within a reasonable timeframe (as determined by
the PSNA) the IP address allocation will be revoked.
In addition, if any service provider or submitter allocations are
left unused or found to be significantly underutilised
(determined by the PSNA) after a period of 6 months from
initial request approval, the IP address allocation will be
revoked
TEL Telephony: from "PSN Technical Domain Description v2.3"
TEL.1 Telephony All service providers must adhere to the technical standards, Solution Design and SHALL PSNSP
deployment methodologies and best practice Demonstration.
recommendations as detailed in the Technical Domain
Description.
TEL.2 Telephony Telephony Servers must support interoperation using RFC Solution Design and SHALL PSNSP
3261: „SIP Session Initiation Protocol‟. Demonstration.
TEL.3 Telephony The service provider should support the SIP location identifier Solution Design and SHOULD PSNSP
option in response to a specific request for compliance with a Demonstration.
third-party system specification.
TEL.4 Telephony Codec selection will be in accordance with RFC 3264 Solution Design and SHALL PSNSP
Demonstration.
UNCLASSIFIED Page B: Tech: 23UNCLASSIFIED
PSN Code Template exemplar Website Version V1 0 Once completed, this document takes the classification of the system it describes Technical Interoperability
Technical Interoperability - Customers do not have to fill in anything on this sheet
Id Subject Obligation Compliance Priority Applies To Compliant Supporting Evidence
(Y/N/Waiver)
TEL.5 Telephony Negotiation between PSN servers shall be as specified in Solution Design and SHALL PSNSP
RFC 3264. Demonstration.
TEL.6 Telephony The Transport Protocol for SIP between PSN servers shall be Solution Design and SHALL PSNSP
as specified in RFC 3261 „Session Initiation Protocol‟. Demonstration.
TEL.7 Telephony Network Authentication will be achieved through the use of a Solution Design and SHALL PSNSP
trusted IP Address. Demonstration.
TEL.8 Telephony The media transport protocol for PSN telephony is as Solution Design and SHALL PSNSP
specified in RFC 3550 RTP: A Transport Protocol for Real- Demonstration.
Time Applications.
TEL.9 Telephony PSN requires Support for Facsimile and this must be in Solution Design and SHALL PSNSP
accordance with RFC 3362: Real-Time Facsimile (T.38). Demonstration.
TEL.10 Telephony PSN requires that RFC 2833: RTP Payload for Dual Tone Solution Design and SHALL PSNSP
Multi frequency (DTMF) Digits, Telephony Tones and Demonstration.
Telephony signals is supported. Data Modem support is not
required.
TEL.11 Telephony The service provider will support CLI as a default Solution Design and SHALL PSNSP
requirement. CLI may be suppressed at the client‟s request. Demonstration.
Transport of CLI will be in accordance with RFC 3325 Private
Extensions to the Session Initiation Protocol (SIP) for
Asserted Identity within Trusted Networks.
TEL.12 Telephony The service provider will support RFC 3323 A Privacy Solution Design and SHALL PSNSP
Mechanism for the Session Initiation Protocol (SIP). Demonstration.
TEL.13 Telephony PSN servers will support fixed and variable number length. Solution Design and SHALL PSNSP
Demonstration.
TEL.14 Telephony The service provider will support system transition to the PSN Solution Design and SHALL PSNSP
through continued support and maintenance of the external Demonstration.
Direct Dial Inward (DDI) numbering geographic or otherwise.
UNCLASSIFIED Page B: Tech: 24You can also read
