KITE¶

The KITE protocol allows registering prefixes using "authenticated" Interest-Data exchanges between a mobile producer (MP) and a trusted Rendezvous Server (RV). The Interest leaves traces in the stateful forwarding plane (PIT entries), constructing a forwarding path to the MP. The term "authenticated" refers to the fact that the RV will verify the information carried in the Interest (primarily the signature), and respond with Data only for legitimate Interests. The Data sent by the RV will trigger intermediate forwarders to save the forwarding path as RIB entries, for a prefix specified by the name of the corresponding Interest/Data.

KITE Acknowledgment object (KiteAck)¶

The KITE acknowledgment object is a Data packet sent by the RV for an Interest (a KITE request) that passes verification. A KITE request is essentially a command Interest, and a KITE request that passes the verification is supposed to be sent by the owner of the prefix for which the forwarding path is set up.

A Data packet that satisfies the following requirements is a KITE acknowledgement object:

• Name starts with a prefix announced by an RV, followed by a fixed "32=KITE" keyword name component, followed by one or more name components.
• ContentType is 6 (KITE Acknowledgment).
• Carry a prefix announcement object as payload, and the "announced prefix" indicated by the PA object must be the same as the name of the KiteAck minus the "32=KITE" keyword component (excluding Interest signature related components and the Parameters digest component).
• The payload only consists of a prefix announcement object in data form, no other content.