Naval Association of Canada, 22 March 2021 There is a need for the RCN to be able to operate both with allies and alone as required. This is where the […]
*Moderator’s Note: Portions of this article appeared originally as “The History and Theory of Naval Effects-Based Operations” in Effects-Based Approaches to Operations: Canadian Perspectives, Alan English and Howard Coombs, eds., […]
*Moderator’s Note: This article was original published in The Nova Scotian on 11 September 2011. At approximately 9:00 am this morning, the United States Consul-General to Halifax will be joined […]
[*Moderator’s Note: This article appeared originally as part of the ‘Plain Talk’ series in the Fall 2010 issue (Vol. 6, No. 3) of Canadian Naval Review.] Is the announcement of […]
Re: David Pugliese’s article “Navy passes on shifting more ships to the Pacific” on 09 May, 2008. The balance of warships between East and West has been debated since the […]
It seems to me that Airedale is expressing frustration at the lack of a comprehensive explanation by the navy about how the future fleet plans make it any better able […]
Everything that Peter Haydon says in his article on the “Canadian Naval Task Group” is accurate. The task group has been fundamental to our past success and it will likely […]
As its operational focal point, the modern Canadian navy uses a “multi-purpose, combat-capable task group.” This policy is consistent with the 1994 Defence White Paper which calls for the navy […]
The report of the arrival of France’s F.N. Tonnerre in Halifax should raise some issues for Canada. Tonnerre is a four-in-one vessel – helicopter carrier, hospital ship, command ship, and […]
For much of February 2007, a small group of academics that included serving and former naval officers engaged in an electronic debate on the future of Canada’s defence and naval […]
Cookie Consent
At Canadian Naval Review (CNR), we are committed to respecting your privacy. This commitment extends to our use of cookies and other tracking technologies such as Google Analytics, browser cookies and user tokens (“cookies”).
When you visit our website for the first time (or use a new browser), a banner will appear on the page that allows you to set your cookie preferences. You will be asked to either “Accept all” cookies (including ‘non-essential cookies’) or “Customize” your cookie preferences, which allows you to make individual choices and get details on the cookies we use.
Contains information related to marketing campaigns of the user. These are shared with Google AdWords / Google Ads when the Google Ads and Google Analytics accounts are linked together.
90 days
__utma
ID used to identify users and sessions
2 years after last activity
__utmt
Used to monitor number of Google Analytics server requests
10 minutes
__utmb
Used to distinguish new sessions and visits. This cookie is set when the GA.js javascript library is loaded and there is no existing __utmb cookie. The cookie is updated every time data is sent to the Google Analytics server.
30 minutes after last activity
__utmc
Used only with old Urchin versions of Google Analytics and not with GA.js. Was used to distinguish between new sessions and visits at the end of a session.
End of session (browser)
__utmz
Contains information about the traffic source or campaign that directed user to the website. The cookie is set when the GA.js javascript is loaded and updated when data is sent to the Google Anaytics server
6 months after last activity
__utmv
Contains custom information set by the web developer via the _setCustomVar method in Google Analytics. This cookie is updated every time new data is sent to the Google Analytics server.
2 years after last activity
__utmx
Used to determine whether a user is included in an A / B or Multivariate test.
18 months
_ga
ID used to identify users
2 years
_gali
Used by Google Analytics to determine which links on a page are being clicked
30 seconds
_ga_
ID used to identify users
2 years
_gid
ID used to identify users for 24 hours after last activity
24 hours
_gat
Used to monitor number of Google Analytics server requests when using Google Tag Manager