Change Control Notice
IPfix CUG clarification
30th March 2020
HSCN Obligations Framework – Technical and Security Obligations – TOW1
Amend the current TOW1 obligation, adding “IPfix data for traffic that remains local to a community need only be sent to the HSCN Authority’s Network Analytics Service (NAS) if requested by the HSCN consumer”.
TOW1 currently reads as the following with the added text in red.
The HSCN Supplier shall establish mechanisms enabling communities of interest to communicate via a regional network architecture. The communities may be associated by regional, functional or organisational parameters. This service will support consumer specific closed user groups as well as the standard HSCN routing mechanisms. – IPfix data for traffic that remains local to a community need only be sent to the HSCN Authority’s Network Analytics Service (NAS) if requested by the HSCN consumer.
To correct mistakes or add clarity.
Clarification of obligation after differing behavior observed between CN-SPs and consultation with DSC.
Comments due back by 16th April 2020.
No comment is assumed to be acceptance.
Date posted – 6th April
Is this saying, any IPFIX data that is leaving a CNSP (to either the peering exchange or WWW) needs to be sent to NAS. Any other local to the CNSP does not?
Post expires at 2:06pm on Friday October 1st, 2021