Important Notice: Our web hosting provider recently started charging us for additional visits, which was unexpected. In response, we're seeking donations. Depending on the situation, we may explore different monetization options for our Community and Expert Contributors. It's crucial to provide more returns for their expertise and offer more Expert Validated Answers or AI Validated Answers. Learn more about our hosting issue here.

How do we interpret USGv6 profile requirement recommendations before their published “effective date”? In particular, what does the profile mean prior to July 2010?

0
Posted

How do we interpret USGv6 profile requirement recommendations before their published “effective date”? In particular, what does the profile mean prior to July 2010?

0

The ‘effective date’ of requirements in this profile defines our recommendation of the earliest point by which such requirements should be mandated for general acquisitions. Such target dates represent a careful balance and agreement with the vendor community between forward looking requirements and the development lead times necessary to achieve to them in commercial products. For a given published version of this profile, in the period prior to the effective date of a particular capability/function, users should revert to previous published versions of the profile for the latest requirements that are currently in effect (i.e., their effective date has passed). In cases where there are no prior requirements that are in effect, the current requirement should be considered as completely optional (“O”) from a stock USGv6 profile compliance point of view, until its effective date is passed. Clearly, for the first version of the profile, this means that all requirements are to be considere

Related Questions

What is your question?

*Sadly, we had to bring back ads too. Hopefully more targeted.

Experts123