<?xml version="1.0" encoding="UTF-8"?>
<item xmlns="http://omeka.org/schemas/omeka-xml/v5" itemId="736" public="1" featured="0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://omeka.org/schemas/omeka-xml/v5 http://omeka.org/schemas/omeka-xml/v5/omeka-xml-5-0.xsd" uri="https://declassified.library.utoronto.ca/items/show/736?output=omeka-xml" accessDate="2026-05-31T09:19:55-04:00">
  <fileContainer>
    <file fileId="796">
      <src>https://declassified.library.utoronto.ca/files/original/945d1a8cd1896cd6b368fd917f4efd4b.pdf</src>
      <authentication>3bc47d61b230c774cef1ccd00e1162e0</authentication>
      <elementSetContainer>
        <elementSet elementSetId="31">
          <name>PDF Text</name>
          <description/>
          <elementContainer>
            <element elementId="131">
              <name>Text</name>
              <description/>
              <elementTextContainer>
                <elementText elementTextId="2374">
                  <text>TO EXTERNAL
2487 OPIMMED
REF OURTEL
2462 OCT24

BERLINCONTINGENCY
atl A F.ORM
OF APPROVAL
FOR BERCON/MARC~
PLANSWHICHWOULD
BE

CLOSETO WHATYOUSUGGESTED
IN YOURTEL
DL1509 OCT19.I HAVEDI~~~~­
SUCHA FORMULA
WITHA NUMBER
OF MYCOLl.,.EAGUES
PRIVATELY
ANOBELIEVE
IT WOULD
BE GENERALLY
ACCEPTABLE.
2oCHANGES
OF IMPORTANCE
WOULD
BE CONFINED
TO PARA8CB)Cll&gt;OFP0/62/641~
IN PARTICULAR
OPENINGPHRASES.SUGGESTED
REVISEDFORMULA
WOULD
READ
QUOTECOUNCILAPPROVED
IN PRINCIPLEANDFOR PLANNING
PURPOSES
MAJOR
NATOCMDRSPLANSUNQUOTE.REMAINDER
OF PARA8CB)Cll)WOULD
REMAIN
~CHANGEDSO WOULD
PARASB&lt;
BH I&gt; ANDSCBH III&gt;.
3oFINLETTERLIKE BRIT FRENCHANDSEVERALOTHERPERMREPS,ISAUTHOR•
!ZED TO ACCEPTFORMULA
AS IT APPEARSIN PARAS&lt;
B&gt; TOF P0/62/641.
NEVERTHLESS
KE WOULD
BE PREPARED
TO ACCEPTOURFORMULA
SO LONG
AS HE COULDSAYTHAT,FORHIS PART,HEUNDERSTOOD
IT TO AMOUNT
TO
SAMETHINGAS VERSIONIN P0/62/641.HE UNDERSTOOD
THATIT WOULD
PROBABLY
BE NECESSARY
FOR US,ASSUMING
THIS FORNULA
IS ACCEPTABLE
TO MINISTERS,TOMAKEA STATEMENT
FOR RECORD
REITERATING
OURPOSIT•
ION ONNUCLEAR
WEAPONS
ANDPARALLEL
POLITICALPLANNINGoKE
APPEALED
TO MEHOWEVER
NOTRPT NOTTO CASTTHESESTATEMENTS
IN FORMOF
RESERVATIONS
ORCONDITIONS
FORMALLY
MODIFYING
OURACCEPTANCE.HIS
SOLEINTERESTHE TOLDMEBOTHONMILITARYPLANNING
ANDON ECONOMIC
COUNTERMEASURES
IS TO GETTHESESUBJECTSOUTOF THE WAYANDOFF THE
COUNCILSAGENDA
AS BONESOF COOTENTION.HE
RECOGNIZES
THATAS AN
EXERCISEIN ATTEMPTING
TO CONTROL
MILITARYPLANNING
THROUGH
COONCIL
BERLINCONTINGENCY
PLANNING
HASNOTRPT Na£ BEENVERYSUCCESSFUL.
WHILEUSAANDBRIT DLS AREREADY
ANDANXIOUS
TO PROCEED
WITHCON•
SULTATIONS
ONPARRALLEL
POLITICALPLANINGFINLETTEREXPLAINED
••• 2

000696

�ira,ub~f
~~~~J
PAGE TWO 2487

FEB2 7 JUI§

THATBECAUSE
OF FRENCHATTITUDETHEREHADBEENDIFFICULTYIN
BEINGFORTHCOMING
SO FAR. SINCE
CHANGE IT

WOULD
CREATE VERY

FRENCH ATTITUDE
WAS UNLIKELY
TO

GREAT DIFFICULTIESF CR USAAND UK

IN

CONTRIBUTING
TO DISCUSSIONONPARALLEL
POLITICALPLANNING
IF OTHER
MEMBERS
OF COUNCILINSISTEDON OPENING POLITICALDISCUSSION
ON
BASIS OF AGREED
TRIPARTITE POLITICAL PAPERS·EQUIVALENT
TO AGREED
TRIPARTITEMILITARYPAPERSWHICHHADBEENINTRODUCED
AS A BASIS
FOR DISCUSSION OF MILITARY CONTINGENCY
PLANNING.

4ol SHOULD
APPRECIATE
HAVINGYOURAUTHORITY
AS EARLYAS POSSIBLE
TO INDICATECONWILLINGNESS
TO ACCEPTCOMPROMISE
FORMULA
FOR APPROVAL
&lt;F

BERCON/MARCON
PLANSINDICATED
ABOVE,AS
WELLAS AN INDICATIONOF

POINTS~HICHI WOULD
HOPEYOUWOULD
BE ABLETO AUTHORIZE
METO
STATEFOR RECORD
OF COUNCILAS AN UNDERSTANDING
OF IMPLICATICJIJS
OF
DECISION,RATHER
THANAS A CONDITION
OF ACCEPTANCE
OR A RESERVATION
IGNATIEFF

000697

�</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </file>
  </fileContainer>
  <collection collectionId="26">
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="1286">
                <text>NATO</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </collection>
  <elementSetContainer>
    <elementSet elementSetId="1">
      <name>Dublin Core</name>
      <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
      <elementContainer>
        <element elementId="50">
          <name>Title</name>
          <description>A name given to the resource</description>
          <elementTextContainer>
            <elementText elementTextId="996">
              <text>Berlin Crisis / 25 OCTOBER 1962 </text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="40">
          <name>Date</name>
          <description>A point or period of time associated with an event in the lifecycle of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="4506">
              <text>1962-10-25</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="42">
          <name>Format</name>
          <description>The file format, physical medium, or dimensions of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="4511">
              <text>PDF</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="44">
          <name>Language</name>
          <description>A language of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="4516">
              <text>en</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="51">
          <name>Type</name>
          <description>The nature or genre of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="4521">
              <text>Text</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="43">
          <name>Identifier</name>
          <description>An unambiguous reference to the resource within a given context</description>
          <elementTextContainer>
            <elementText elementTextId="4526">
              <text>CDTT00046</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="48">
          <name>Source</name>
          <description>A related resource from which the described resource is derived</description>
          <elementTextContainer>
            <elementText elementTextId="7996">
              <text>NATO Paris to External Affairs, "Berlin Contingency,’’ 25 Oct. 1962, LAC, RG 25, vol. 6080, file no. 50341-A-2-40, part 2.</text>
            </elementText>
          </elementTextContainer>
        </element>
      </elementContainer>
    </elementSet>
  </elementSetContainer>
  <tagContainer>
    <tag tagId="1068">
      <name>BERCON plans</name>
    </tag>
    <tag tagId="1131">
      <name>Berlin contingency</name>
    </tag>
    <tag tagId="1073">
      <name>Marcon Series</name>
    </tag>
    <tag tagId="1136">
      <name>Thomas Finletter</name>
    </tag>
  </tagContainer>
</item>
