BBN STC

10 Moulton Street Cambridge MA 02238 (617) 873-4323 dwaitzman@BBN.COM http://bbn.com

BBN STC

10 Moulton Street Cambridge MA 02238 (617) 873-4323 opoudjis@gmail.com http://opoudjis.net

Internet Network Working Group Avian carriers can provide high delay, low throughput, and low altitude service. The connection topology is limited to a single point-to-point path for each carrier, used with standard carriers, but many carriers can be used without significant interference with each other, outside of early spring. This is because of the 3D ether space available to the carriers, in contrast to the 1D ether used by IEEE802.3. The carriers have an intrinsic collision avoidance system, which increases availability. Unlike some network technologies, such as packet radio, communication is not limited to line-of-sight distance. Connection oriented service is available in some cities, usually based upon a central hub topology. Yes, this is an April Fool's RFC.

Frame Format The IP datagram is printed, on a small scroll of paper, in hexadecimal, with each octet separated by whitestuff and blackstuff. The scroll of paper is wrapped around one leg of the avian carrier. A band of duct tape is used to secure the datagram's edges. The bandwidth is limited to the leg length. The MTU is variable, and paradoxically, generally increases with increased carrier age. A typical MTU is 256 milligrams. Some datagram padding may be needed.alt Upon receipt, the duct tape is removed and the paper copy of the datagram is optically scanned into a electronically transmittable form. This document extends OpenPGP and its ECC extension to support SM2, SM3 and SM4:

• support the SM3 hash algorithm for data validation purposes
• support signatures utilizing the combination of SM3 with other digital signing algorithms, such as RSA, ECDSA and SM2
• support the SM2 asymmetric encryption algorithm for public key operations
• support usage of SM2 in combination with supported hash algorithms, such as SHA-256 and SM3
• support the SM4 symmetric encryption algorithm for data protection purposes
• defines the OpenPGP profile "OSCCA-SM234" to enable usage of OpenPGP in an OSCCA-compliant manner.

Algorithm-Specific Fields for SM2DSA keys:

• a variable-length field containing a curve OID, formatted as follows:
  1. a one-octet size of the following field; values 0 and 0xFF are reserved for future extensions
  2. octets representing a curve OID.
• MPI of an EC point representing a public key

Definitions

OSCCA-compliant:

All cryptographic algorithms used are compliant with OSCCA regulations.

SM2DSA:

The elliptic curve digital signature algorithm.

SM2KEP:

The elliptic curve key exchange protocol.

SM2PKE:

The public key encryption algorithm.

Elliptic Curve Formula $$ y^2 = x^3 + ax + b $$ (1)

Curve Parameters

Curve Parameters Listing

Code to launch spaceship module Foo class Bar def prepare_launch(spaceship, rocket) spaceship.load_personnel rocket.load(spaceship) rocket end end end ]]>

Supported Algorithms

Public Key Algorithms The SM2 algorithm is supported with the following extension. The following public key algorithm IDs are added to expand Section 9.1 of RFC4880, "Public-Key Algorithms": Table 2

ID	Description of Algorithm
TBD	SM2

Security Considerations Security is not generally a problem in normal operation, but special
measures MUST be taken (such as data encryption) when avian carriers are used in a tactical environment.,

Normative References International Organization for Standardization International Electrotechnical Commission ISO/IEC 10118-3 Informative References IRTF OCBAEADauthenticated-encryption This document specifies OCB, a shared-key blockcipher-based encryption scheme that provides confidentiality and authenticity for plaintexts and authenticity for associated data. This document is a product of the Crypto Forum Research Group (CFRG).