ADDITIONAL INFORMATION ON TEST PROCEDURES

This appendix is a mandatory part of this specification. The information contained herein is intended for compliance. This appendix is to provide additional information to the user of this specification in performing the voltage standing wave ratio, RF leakage, and insertion loss tests.

\n\n\n\nA.2TEST TYPES\nA.2.1\n

Voltage standing wave ratio (see 4.6.11).

\nA.2.1.1Test connector\n

The standard test-connector interface shall be in accordance with MIL-STD-348. The standard test connector impedance shall be 50 ± 0.5 ohms.

\n\n\n\n\nA.3MEASUREMENTS\nA.3.1\n

RF leakage (see 4.6.23).

\nA.3.1.1Measurement technique\n

The measurement of the leakage from connectors is performed by collecting the leakage energy in a coaxial system surrounding the leakage source. An outline of the instrumentation is shown on figure 7.

For direct leakage measurements the adjustable short circuit serves several purposes.

The short-circuit position is adjusted to assure that an adequately low impedance appears behind the equivalent leakage generator. A matched termination can be substituted, but the resulting 6-dB loss cannot be tolerated in some cases. In addition, if the leakage source is directional, as it indeed is for connectors with multiple leakage, it is possible for the leakage to be directed to this termination at some frequencies and not collected by the detector. For surface transfer-impedance measurements on connectors with leakage from more than one point in the connector, however, a matched termination is desirable in order to simplify the transformation of the measured data to absolute transfer impedance data. This is not needed to make relative comparisons in this test.

\n\n\n\n\n\n","type":"text"}]}]},{"type":"layoutColumn","attrs":{"width":33.33},"content":[{"type":"paragraph"}]}]},{"type":"layoutSection","content":[{"type":"layoutColumn","attrs":{"width":66.66},"content":[{"type":"heading","attrs":{"level":1},"content":[{"text":"Example 2: References/Bibliography","type":"text"}]},{"type":"paragraph","content":[{"text":"The following example shows a properly styled document reference list. ","type":"text"}]},{"type":"paragraph","content":[{"text":"Bibliography items may or may not be cited in the document body; references typically are cited. ","type":"text"}]},{"type":"panel","attrs":{"panelType":"warning"},"content":[{"type":"paragraph","content":[{"text":"Bibliography and reference items are distinct from normative references, which are indispensable to the application of the standard.","type":"text"}]}]}]},{"type":"layoutColumn","attrs":{"width":33.33},"content":[{"type":"paragraph"}]}]},{"type":"layoutSection","content":[{"type":"layoutColumn","attrs":{"width":66.66},"content":[{"type":"heading","attrs":{"level":2},"content":[{"text":"Word Sample","type":"text"}]},{"type":"mediaSingle","attrs":{"layout":"center","width":81.0},"content":[{"type":"media","attrs":{"width":774,"alt":"Screenshot in Draft View of a reference section. It has already been fully color-coded with tags and character styles. The Reference Head is styled as BiblioHead, and all the references are styled as BiblioEntry","id":"ba28203a-301a-407e-a305-4df694c78ffa","collection":"contentId-2946727984","type":"file","height":484}}]}]},{"type":"layoutColumn","attrs":{"width":33.33},"content":[{"type":"paragraph"}]}]},{"type":"layoutSection","content":[{"type":"layoutColumn","attrs":{"width":66.66},"content":[{"type":"heading","attrs":{"level":2},"content":[{"text":"XML Sample","type":"text"}]},{"type":"paragraph","content":[{"text":"eXtyles leverages the character-styling of the reference list (applied during ","type":"text"},{"text":"Standards Reference Processing","type":"text","marks":[{"type":"link","attrs":{"__confluenceMetadata":{"isRenamedTitle":true,"linkType":"page","contentTitle":"Standards Bibliographic and Normative Reference Processing","versionAtSave":"14"},"href":"/wiki/spaces/EUDR/pages/2374074439"}}]},{"text":") to add granular tagging to the reference entries (e.g. , , and ).","type":"text"}]},{"type":"codeBlock","content":[{"text":"\n\nReferences\n1

Acar

, Backes

, Fahl

, Kim

, Mazurek

, Stransky

(2016) You get where you’re looking for: The impact of information sources on code security. Proceedings of the 37th IEEE Symposium on Security and Privacy, pp 289–305.

\n2

Duong

, Rizzo

(2011) Cryptography in the web: The case of cryptographic design flaws in ASP.NET. Proceedings of the 31st IEEE Symposium on Security and Privacy, pp 481–489.

\n3

Egele

, Brumley

, Fratantonio

, Kruegel

(2013) An empirical study of cryptographic misuse in Android applications. Proceedings of the 2013 ACM SIGSAC Conference on Computer & Communications Security (CCS ’13), pp 73–84.

\n4

Fahl

, Harbach

, Muders

, Baumgartner

, Freisleben

, Smith, M (2012) Why Eve and Mallory love Android: An analysis of Android SSL (in)security. Proceedings of the 2012 ACM Conference on Computer and Communications Security (CCS ’12), pp 50–61.

\n5

Nadi

, Kruger

, Mezini

, Bodden

(2016) Jumping through hoops: Why do Java developers struggle with cryptography APIs? Proceedings of the 38th International Conference on Software Engineering (ICSE ’16), pp 935–946.

\n6

Haney

, Theofanos

, Acar

, Prettyman

(2018) “We make it a big deal in the company”: Security mindsets in organizations that develop cryptographic products. Proceedings of the 14^th Symposium on Usable Privacy and Security, pp 357-373.

\n7

National Institute of Standards and Technology (2001) Security requirements for cryptographic modules, Federal Information Processing Standard Publication 140-2, http://csrc.nist.gov/publications/fips/fips140-2/fips1402.pdf [accessed 8/1/2018]

\n\n","type":"text"}]}]},{"type":"layoutColumn","attrs":{"width":33.33},"content":[{"type":"paragraph"}]}]},{"type":"paragraph"}],"version":1}

Browser not supported