<?xml version='1.0' encoding='utf-8'?>
<!DOCTYPE rfc [
  <!ENTITY nbsp    "&#160;">
  <!ENTITY zwsp   "&#8203;">
  <!ENTITY nbhy   "&#8209;">
  <!ENTITY wj     "&#8288;">
]>
<?xml-stylesheet type="text/xsl" href="rfc2629.xslt" ?>
<!-- generated by https://github.com/cabo/kramdown-rfc version 1.7.43 (Ruby 3.2.3) -->
<rfc xmlns:xi="http://www.w3.org/2001/XInclude" ipr="trust200902" docName="draft-slutsky-homing-pigeon-v2-04" category="info" submissionType="independent" tocInclude="true" sortRefs="true" symRefs="true" version="3">
  <!-- xml2rfc v2v3 conversion 3.35.0 -->
  <front>
    <title abbrev="Homing Pigeon v2">Homing Pigeon Message Protocol, Version 2: Determinations, Questions, and Shared Context</title>
    <seriesInfo name="Internet-Draft" value="draft-slutsky-homing-pigeon-v2-04"/>
    <author initials="A." surname="Slutsky" fullname="Andrew Slutsky">
      <organization>Independent</organization>
      <address>
        <email>slutsky5544@gmail.com</email>
      </address>
    </author>
    <date year="2026" month="November" day="15"/>
    <keyword>determination</keyword>
    <keyword>question</keyword>
    <keyword>answer</keyword>
    <keyword>context segment</keyword>
    <abstract>
      

<t>This document specifies version 2 of the Homing Pigeon message
protocol. Version 2 is an addition to version 1
(draft-slutsky-homing-pigeon), not a replacement for it: every version 1
message keeps its meaning, and version 2 adds three messages and one
mechanism on top of the version 1 exchange.</t>
      <t>The additions are a determination message, by which the runner tells
the submitter what it expects a job to do before the job runs; a
question message, by which a runner whose local decision machinery
cannot answer a question itself asks that question instead; an
answer message, by which any enabled holder of the shared secret
replies; and context segments, signed fragments of local state
that travel with these messages and with the version 1 result, so
each side plans with the other's actual state in view.</t>
      <t>Version 2 is backwards compatible. A version 1 runner never sends a
version 2 message and is unaffected by this document. A submitter
that implements this document adapts to the protocol version the
runner supports: faced with a version 1 runner, it submits version 1
jobs and expects version 1 results, exactly as before. There is no
version negotiation and no handshake; the messages carry <tt>v</tt>, as in
version 1, and each side acts on what it receives.</t>
      <t>The deployment that motivates version 2 is the constrained runner: a
small host whose local decision machinery is deliberately
deterministic and carries no language model. Version 1 leaves such a
runner alone with every question its deterministic machinery cannot
answer. Version 2 lets it ask.</t>
    </abstract>
  </front>
  <middle>
    

<section anchor="introduction">
      <name>Introduction</name>
      <t>Version 1's core exchange is two messages: a signed job object and a
signed result object, carried unchanged over any binding. The runner's decisions in version 1 are
local: it verifies the signature and the further admission checks of
its Section 14, forms whatever expectation its configuration gives
it, executes, and reports an exit code and output. The result may
carry the runner's opinion home as the <tt>oracle_opinion</tt> member, but
that opinion is formed and frozen on the runner alone: the submitter
has no way to ask a question before execution, and the runner has no
way to ask one at all.</t>
      <t>Three gaps follow, and version 2 closes each with one message:</t>
      <ol spacing="normal" type="1"><li>
          <t>The submitter cannot see the runner's expectation before the
run. A runner that expects a job to fail - because the box is
hot, the disk is failing, or the same job failed an hour ago -
has no way to say so until the result returns. The determination
message (Section 6) is that statement, sent before execution.</t>
        </li>
        <li>
          <t>A constrained runner cannot escalate. Where a full runner asks
its local model and folds the reply into its decision, a
deterministic runner has only its default. The question message
(Section 7) carries the question the runner would have asked its
own model to the submitter, and the answer message (Section 8)
carries the reply back as a signed object.</t>
        </li>
        <li>
          <t>Each side plans from a partial picture. The submitter sees exit
codes; the runner sees one job at a time. Context segments
(Section 10) are the shared remedy: signed, append-only fragments
of state and reasoning that ride the messages both ways, so the
submitter plans its next job from the runner's actual state, and
the runner's components share what they observe with each other
and with the submitter.</t>
        </li>
      </ol>
      <section anchor="who-decides-what">
        <name>Who decides what</name>
        <t>Every message in this document exists to move one decision to the
side that can make it. The figures in this document are normative in
intent if not in form: an implementation that moves a decision to
the wrong side of a figure has misunderstood the protocol.</t>
        <artwork><![CDATA[
                    DECISION              DECIDED BY
                    -------------------   -------------------
                    admit or refuse job   the runner, on the
                                          signature and its own
                                          admission checks (v1)

                    what the job will     the runner, before
                    probably do           execution (determination)

                    a question the        an enabled answerer,
                    runner cannot         if it answers in time
                    answer locally

                    the same question       the runner, by its
                    after the deadline    local default

                    what runs, finally    the runner, always;
                                          no answer admits a job

                    the next job          the submitter, with
                                          the runner's context
                                          in view
]]></artwork>
      </section>
      <section anchor="backwards-compatibility-and-adaptation">
        <name>Backwards compatibility and adaptation</name>
        <t>Version 2 changes no version 1 message. A version 2 runner <bcp14>MUST</bcp14>
accept version 1 jobs and <bcp14>MUST</bcp14> answer them with version 1 results.
A version 2 message is sent only when the operator has enabled
version 2 on that runner (Section 11), and only ever concerns a
job that was itself admissible under version 1 rules.</t>
        <t>A submitter that implements this document will routinely face
runners that do not. Realizing a runner does not support version 2 -
because no version 2 message ever arrives from it, or because the
operator says so - is not an error and needs no machinery: the
submitter falls back to version 1 with that runner, submitting
version 1 jobs and reading version 1 results. The submitter adapts
to the protocol version the endpoint supports; the endpoint is never
asked to adapt, to negotiate, or to announce itself.</t>
        <artwork><![CDATA[
   Submitter (v2)                       Runner
        |                                  |
        |  job (v=1 object, as always)     |
        |--------------------------------->|
        |                                  |
        |        if the runner is v2 and   |
        |        the operator enabled it:  |
        |                                  |
        |  determination (v=2)             |
        |<---------------------------------|
        |  question (v=2)                  |
        |<---------------------------------|
        |  answer (v=2)                    |
        |--------------------------------->|
        |                                  |
        |  result (v=1 object, with        |
        |   context segments attached)     |
        |<---------------------------------|
        |                                  |
        |        if the runner is v1:      |
        |        none of the v2 lines      |
        |        above ever happen, and    |
        |        the exchange is exactly   |
        |        the version 1 exchange.   |
]]></artwork>
      </section>
    </section>
    <section anchor="requirements-language">
      <name>Requirements Language</name>
      <t>The key words "<bcp14>MUST</bcp14>", "<bcp14>MUST NOT</bcp14>", "<bcp14>REQUIRED</bcp14>", "<bcp14>SHALL</bcp14>", "<bcp14>SHALL
NOT</bcp14>", "<bcp14>SHOULD</bcp14>", "<bcp14>SHOULD NOT</bcp14>", "<bcp14>RECOMMENDED</bcp14>", "<bcp14>NOT RECOMMENDED</bcp14>",
"<bcp14>MAY</bcp14>", and "<bcp14>OPTIONAL</bcp14>" in this document are to be interpreted as
described in BCP 14 <xref target="RFC2119"/> <xref target="RFC8174"/> when, and only when, they
appear in all capitals, as shown here.</t>
      

</section>
    <section anchor="terminology">
      <name>Terminology</name>
      <t>The terms of draft-slutsky-homing-pigeon <xref target="I-D.slutsky-homing-pigeon"/> apply: submitter, runner,
binding, shared secret, key_id, and the message members defined
there. This document adds:</t>
      <t>Determination: the runner's pre-execution statement of what it
expects a job to do, and why. A determination is an opinion, formed
from the runner's local state and history, frozen before the job
runs and never revised afterwards.</t>
      <t>Question: a question the runner's local decision machinery would
have put to a local model, sent instead because no local model is
available. The reference software asks only for an exec job, and
only when its Oracle is deterministic.</t>
      <t>Answer: a signed reply to one question, identified by that
question's identifier. The answerer is any holder of a shared
secret the runner already trusts. It does not have to be the
party that submitted the job. One answer decides; a late or
second answer is context and does not vote again. An answer
never admits a job and never changes what runs.</t>
      <t>Local default: the decision the runner makes when no answer has
arrived by the question's deadline. Every question has one; asking
never leaves a decision unmade.</t>
      <t>Deadline: the time by which an answer must arrive to affect the
decision it was asked about. An answer that arrives after its
deadline is not discarded; it becomes context for the next decision
(Section 8).</t>
      <t>Context segment: a signed, self-describing fragment of state or
reasoning, appended to a message by one component and readable by
the others, carrying its author's identity and a seen-once
identifier (Section 10).</t>
      <t>Clean pass: a determination that the job is expected to proceed
without incident: no finding above the runner's lowest severity of
interest, no expected failure, nothing the submitter would act on.
The runner's local policy defines the threshold precisely; the
protocol defines only that the threshold exists (Section 6).</t>
    </section>
    <section anchor="the-exchange-at-a-glance">
      <name>The Exchange at a Glance</name>
      <artwork><![CDATA[
 Submitter                          Runner
    |                                  |
    |  1. job (v1)                     |
    |--------------------------------->|  verify signature (v1 rules)
    |                                  |  form the determination
    |                                  |
    |  2. determination (v2)           |  ONLY if not a clean pass,
    |<---------------------------------|  ONLY if enabled (Sec. 11)
    |                                  |
    |                                  |  a question arises the
    |                                  |  runner cannot answer
    |  3. question (v2)                |
    |<---------------------------------|  deadline starts
    |                                  |
    |  4. answer (v2)                  |  if it arrives in time
    |--------------------------------->|  it rides the result;
    |                                  |  it does not change
    |                                  |  what executes
    |                                  |
    |                                  |  deadline passes with no
    |                                  |  answer: local default
    |                                  |
    |                                  |  execute (v1 rules)
    |  5. result (v1 + segments)       |
    |<---------------------------------|
    |                                  |
 The numbers are the order of first transmission, not a lockstep:
 a determination and a question MAY travel in either order, and
 an answer NEVER delays execution past the deadline.
]]></artwork>
    </section>
    <section anchor="common-form">
      <name>Common Form</name>
      <t>A version 2 message is a JSON object carried on any binding that
carries version 1 messages, byte for byte the same treatment: the
marker and gap conventions of draft-slutsky-homing-pigeon Section 6,
with the message type in the subject as Sections 6, 7, and 8 of this
document specify; the signature and MAC construction of
Section 7 of that document; the per-job encryption of its
Section 16 applied to the whole object; and the common members of
its Section 9, including <tt>v</tt>, which is 2 for the messages this
document defines.</t>
      <t>A receiver that does not implement this document will reject a
message carrying <tt>v</tt> = 2, as version 1 requires it to; that
rejection is the correct and only interaction between a version 2
message and a version 1 receiver, and senders <bcp14>MUST NOT</bcp14> send a
version 2 message on a path where a version 1 receiver is expected
to process it as a job. Version 2 messages are addressed to the
job's <tt>reply_to</tt>. Where a deployment's bindings make that address
and the mailbox a runner polls for jobs the same, the receiving
implementation separates them by type before any job processing.
That addressing rule covers determinations and questions, which are
sent on behalf of a job and carry its <tt>reply_to</tt>. Answers are the
exception: a question carries no <tt>reply_to</tt> of its own, and an
answer is addressed to the runner's own mailbox (or, on another
binding, to the runner's channel), from which the runner reads it.</t>
      <t>Every version 2 message names the job it concerns (<tt>job_id</tt>) and
its own identifier (<tt>msg_id</tt>), and carries <tt>issued_at</tt> as in
version 1. Replay handling follows the seen-set discipline of
version 1: an identifier is recorded once the message has been
acted on, and a duplicate is dropped silently. A receiver <bcp14>MUST</bcp14>
hold <tt>issued_at</tt> to the same window as a version 1 job: its past
window, and the future allowance of version 1 Section 11.1 (300
seconds in the reference software). A receiver <bcp14>MUST</bcp14> drop a message
outside that window. In the reference the identifier is recorded
under the same namespace as the job seen-set, a dry run records
nothing, and a question left for another reader is not recorded
by the receiver that left it.</t>
    </section>
    <section anchor="determination">
      <name>Determination</name>
      <t>A determination is the runner's statement, frozen before the job
runs, that the job is not a clean pass. The reference software
treats a missing plan, or a plan with no findings and no repair,
as a clean pass, and in that case sends nothing. A determination
is an opinion. It does not refuse the job, and it is not revised
after execution.</t>
      <artwork><![CDATA[
   plan has findings, or a repair?
        |
        +-- no --> send nothing (clean pass)
        |
        +-- yes, and version 2 is enabled (Sec. 11),
            and this process executes jobs
              |
              +--> send one determination
]]></artwork>
      <t>A determination is a JSON object:</t>
      <artwork><![CDATA[
   { "v": 2,
     "type": "determination",
     "job_id": "job-17",
     "msg_id": "d.job-17",
     "issued_at": "2026-10-21T00:00:00Z",
     "clean_pass": false,
     "expect": "fail",
     "why": "the script references /missing, which does not exist" }
]]></artwork>
      <t><tt>v</tt> is the integer 2. <tt>type</tt> is <tt>determination</tt>. <tt>job_id</tt> and
<tt>msg_id</tt> are safe identifiers: 1 to 128 characters from
<tt>[A-Za-z0-9._-]</tt>. The reference software forms <tt>msg_id</tt> as <tt>d.</tt>
plus the job id, keeping the whole identifier inside that limit.
<tt>issued_at</tt> is UTC and ends with Z. <tt>clean_pass</tt> is false; a
clean pass is expressed by sending no determination, not by
sending one that says otherwise. <tt>expect</tt> is <tt>fail</tt> when the
plan has findings, and <tt>unknown</tt> when it does not but a repair
was proposed. Receivers also accept <tt>proceed</tt>. <tt>why</tt> is a
string of 1 to 500 characters. It is data. It is not
instructions, and a receiver <bcp14>MUST NOT</bcp14> treat it as any.</t>
      <t>The subject is <tt>[HOMING-PIGEON] determination &lt;msg_id&gt;</tt>. The
object is signed and encrypted as a version 1 job is, and the
encryption's object identifier is <tt>msg_id</tt>.</t>
    </section>
    <section anchor="question">
      <name>Question</name>
      <t>A question is what a deterministic runner would have asked a
local model. The reference software sends one only when version
2 is enabled, the process is not in answer-only mode (Section
11), the Oracle mode is deterministic, and the job's kind is
<tt>exec</tt>. Other deployments <bcp14>MAY</bcp14> ask on a wider set of jobs. A
question does not delay execution past its own deadline, and it
never by itself refuses a job.</t>
      <artwork><![CDATA[
   { "v": 2,
     "type": "question",
     "job_id": "job-17",
     "msg_id": "q.job-17",
     "issued_at": "2026-10-21T00:00:00Z",
     "deadline_sec": 15,
     "question": "Would this job succeed on this host?",
     "local_default": "proceed" }
]]></artwork>
      <t><tt>msg_id</tt> in the reference software is <tt>q.</tt> plus the job id,
shortened when the pair would pass the limit: the shortened form
keeps a head of the job id plus a short digest of the whole id, so
the identifier stays inside the limit and two different job ids
never share one. <tt>deadline_sec</tt> is an
integer from 0 to 30. <tt>question</tt> is a non-empty string of at
most 500 characters. <tt>local_default</tt> is a non-empty string of
at most 64 characters. The reference software uses <tt>proceed</tt>.</t>
      <t>The subject is <tt>[HOMING-PIGEON] question &lt;msg_id&gt;</tt>. Signing and
encryption are as in Section 6, with the object identifier
<tt>msg_id</tt>.</t>
    </section>
    <section anchor="answer">
      <name>Answer</name>
      <t>An answer replies to one question. The answerer is any holder of
a shared secret the runner already trusts, optionally narrowed
to a list of key ids (Section 11). The shared secret is the
credential. The runner cannot tell, and does not need to tell,
which trusted holder produced the answer.</t>
      <artwork><![CDATA[
   { "v": 2,
     "type": "answer",
     "job_id": "job-17",
     "msg_id": "a.q.job-17",
     "question_id": "q.job-17",
     "issued_at": "2026-10-21T00:00:00Z",
     "answer": "it would succeed" }
]]></artwork>
      <t><tt>question_id</tt> is the question's <tt>msg_id</tt>. <tt>msg_id</tt> in the
reference software is <tt>a.</tt> plus that question id, shortened in the
same way when needed. <tt>answer</tt> is a non-empty string of at
most 500 characters. It is data. A runner <bcp14>MUST NOT</bcp14> execute it,
and <bcp14>MUST NOT</bcp14> treat it as admitting the job.</t>
      <t>The subject is <tt>[HOMING-PIGEON] answer &lt;msg_id&gt;</tt>. Signing and
encryption are as in Section 6.</t>
      <t>One answer decides. The reference software records the first
answer for a <tt>question_id</tt> and refuses to replace it. A file
that is not a readable answer does not occupy the slot, so a
crash while saving cannot keep a later answer out. A second
answer, and any answer that arrives after the deadline, is
context for a later decision (Section 10). It does not reopen
the job and it does not vote.</t>
    </section>
    <section anchor="deadline-and-the-local-default">
      <name>Deadline and the Local Default</name>
      <t>The runner sends the determination, if any, and the question,
if any, and then looks for an answer until <tt>deadline_sec</tt>
elapses. The default in the reference software is 0, which
means one look and no wait, so a deployment that has not asked
to wait does not stall a worker. The cap is 30 seconds.</t>
      <artwork><![CDATA[
   question handed to the pipe
        |
        +-- an answer is already filed, or arrives
        |   before the deadline
        |        |
        |        +--> one answer segment on the result
        |
        +-- an answer arrives after the deadline
        |        |
        |        +--> the local default, and a late-answer
        |             segment beside it
        |
        +-- no answer
                 |
                 +--> the local default alone

   Then the job runs, under version 1 rules, either way.
]]></artwork>
      <t>An answer is in time when it was filed at or before the moment
the question was sent, plus <tt>deadline_sec</tt>, plus one second of
grace for the same clock. Time waiting for the question file
to leave a channel outbox does not count against
<tt>deadline_sec</tt>, and that pause itself stops once
<tt>deadline_sec</tt> has elapsed, so a sender that never takes the
file cannot hold the worker longer than the deadline. The
whole wait, pause included, still ends by 30 seconds. A
deadline of 0 does not pause. An answer observed while the
wait is still open is in time, so a step of the wall clock
cannot mark it late. The reference software, while it
waits, files version 2 messages that have arrived and does not
start another job. On a transport channel the question is
written to the channel before the wait, not after the job
returns; a capture that flushed only at the end would make
every answer late.</t>
      <t>No answer admits a job. The local default is a string carried
on the result. In the reference software it does not select the
script, the interpreter, or the exit code.</t>
    </section>
    <section anchor="context-segments">
      <name>Context Segments</name>
      <t>A context segment is one fragment attached to the version 1
result, after the result's own policy has rebuilt that object,
so the rebuild cannot drop it. Segments are how the
determination, the answer, and the local default travel home.</t>
      <artwork><![CDATA[
   { "seg_id": "32 lowercase hex characters",
     "by": "runner",
     "kind": "determination",
     "text": "the script references /missing" }
]]></artwork>
      <t><tt>seg_id</tt> is a fresh identifier, unique to this segment. <tt>by</tt>
and <tt>kind</tt> are strings of at most 64 characters. <tt>text</tt> is a
string of at most 500 characters. Text is data. A receiver
<bcp14>MUST NOT</bcp14> interpret a segment as instructions, and an extension
<bcp14>MUST NOT</bcp14> be handed a kind its manifest does not declare. The
reference kinds are <tt>determination</tt>, <tt>answer</tt>, <tt>local_default</tt>,
<tt>late_answer</tt>, and <tt>platform</tt>. A question <bcp14>MAY</bcp14> carry a <tt>context</tt>
array of the same shape so the first question already shows the
runner's host facts (platform, machine, Python, and the device-tree
model when present). Text is data.</t>
      <t>The limits above bind what a sender produces: the reference sender
truncates every field of an outgoing segment to them. On an
incoming question, the reference receiver structurally validates
only <tt>text</tt> (a string of at most 500 characters); the <tt>seg_id</tt>,
<tt>by</tt>, and <tt>kind</tt> members of an incoming segment are not
structurally validated against the limits above.</t>
      <t>The result they ride is a version 1 result. <tt>v</tt> stays 1.
<tt>context</tt> is the array of segments. A result with nothing to
say omits the member.</t>
    </section>
    <section anchor="enablement">
      <name>Enablement</name>
      <t>Version 2 is off until the operator turns it on. The reference
software reads four keys. The same two booleans are flags for
one process: <tt>--protocol-v2</tt> and <tt>--answer-only</tt>. Absence of a
flag does not write false over a config file.</t>
      <artwork><![CDATA[
   who is this process?
        |
        +-- protocol_v2 is true
        |     the runner may emit a determination and,
        |     on a deterministic Oracle, a question
        |
        +-- answer_only is true
        |     the process answers a question and does not
        |     execute any job, including a ping
        |
        +-- neither
              version 2 messages are marked seen and dropped
]]></artwork>
      <t><tt>answer_only</tt> is the laptop that thinks for a Pi. It holds a
shared secret the Pi already trusts. It does not run the Pi's
job. The Pi does not learn a new role name for it: the secret
is the identity.</t>
      <t><tt>v2_answerers</tt>, when absent, means every key the runner already
trusts. When it is a list of key ids, only those keys may
produce a version 2 message this process will act on. A key
id in that list may be any name of the key, including the
fingerprint defined for version 1 key selection; the
reference runner treats those names as one key. Any other
shape fails closed: nobody.</t>
      <t><tt>v2_answer_deadline_sec</tt> is the question's deadline. Values
outside 0..30 are clamped into that range. The default is 0.</t>
    </section>
    <section anchor="bindings-and-subjects">
      <name>Bindings and Subjects</name>
      <t>Version 2 messages use the bindings of version 1. On the email
binding the subject is <tt>[HOMING-PIGEON]</tt> followed by the message
type and the <tt>msg_id</tt>, as Sections 6, 7, and 8 specify. A
receiver dispatches on that type before it considers the
message a job. A subject that does not match the body's <tt>type</tt>
and <tt>msg_id</tt> is rejected.</t>
      <t>The signature and the encryption are the version 1
constructions. The encryption's object identifier is the
<tt>msg_id</tt> in the subject. Cleartext is refused wherever a
cleartext job is refused.</t>
      <t>A version 2 message is not a job. A job with <tt>v</tt> other than 1
is still rejected. A process that has not enabled version 2
marks the message seen and does not act on it. A process that
has enabled version 2 but is not in <tt>answer_only</tt> mode does not
answer a question and does not mark that question seen, so another
reader of the same mailbox can still answer it. The mode is the
gate (Section 11's figure): <tt>answer_only</tt> is what makes a process
an answerer, while the <tt>v2_answerers</tt> list of Section 11 gates
which keys' messages a process will act on, not whether the
process itself answers. An invalid
question is still rejected and marked seen. A determination
is still marked seen.</t>
    </section>
    <section anchor="security-considerations">
      <name>Security Considerations</name>
      <t>Version 2 extends trust along a line version 1 already drew.
The holder of a shared secret the runner trusts may submit a
job. The same holder, or another holder of a secret the runner
trusts, may answer a question. The operator chooses that set,
and may narrow it to named key ids. Enabling the feature is
what makes the extension; the default is the version 1
exchange, unchanged.</t>
      <t>An answer is not an authorization to run. The runner decides
what runs, before and after the answer, under version 1 rules.
Context text is data. A segment that says to run a different
script is still a segment, and the script that runs is the one
in the job.</t>
      <t>One answer decides, because two answerers would be a race the
protocol does not adjudicate. The first answer filed wins. A
later one cannot replace it and cannot reopen the job.</t>
      <t>The deadline is capped so a question cannot stall a worker past
30 seconds. A deadline of 0 does not wait. Callers that need a
live reply set a deadline long enough for their binding to
carry the question out and the answer back.</t>
      <t>Answer-only mode is a refusal to execute. A process in that
mode will not run a job that shares its mailbox, including a
liveness ping.</t>
    </section>
    <section anchor="iana-considerations">
      <name>IANA Considerations</name>
      <t>This document defines no new IANA registry. The message types
<tt>determination</tt>, <tt>question</tt>, and <tt>answer</tt>, and the integer
version 2, are defined here for use with the Homing Pigeon
message protocol. The version 1 message types are unchanged.</t>
    </section>
  </middle>
  <back>
    <references anchor="sec-normative-references">
      <name>Normative References</name>
      <reference anchor="I-D.slutsky-homing-pigeon">
        <front>
          <title>Homing Pigeon Message Protocol, Version 1</title>
          <author initials="A." surname="Slutsky" fullname="Andrew Slutsky">
            <organization/>
          </author>
          <date year="2026" month="October"/>
        </front>
        <seriesInfo name="Internet-Draft" value="draft-slutsky-homing-pigeon"/>
      </reference>
      <reference anchor="RFC2119">
        <front>
          <title>Key words for use in RFCs to Indicate Requirement Levels</title>
          <author fullname="S. Bradner" initials="S." surname="Bradner"/>
          <date month="March" year="1997"/>
          <abstract>
            <t>In many standards track documents several words are used to signify the requirements in the specification. These words are often capitalized. This document defines these words as they should be interpreted in IETF documents. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.</t>
          </abstract>
        </front>
        <seriesInfo name="BCP" value="14"/>
        <seriesInfo name="RFC" value="2119"/>
        <seriesInfo name="DOI" value="10.17487/RFC2119"/>
      </reference>
      <reference anchor="RFC8174">
        <front>
          <title>Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words</title>
          <author fullname="B. Leiba" initials="B." surname="Leiba"/>
          <date month="May" year="2017"/>
          <abstract>
            <t>RFC 2119 specifies common key words that may be used in protocol specifications. This document aims to reduce the ambiguity by clarifying that only UPPERCASE usage of the key words have the defined special meanings.</t>
          </abstract>
        </front>
        <seriesInfo name="BCP" value="14"/>
        <seriesInfo name="RFC" value="8174"/>
        <seriesInfo name="DOI" value="10.17487/RFC8174"/>
      </reference>
    </references>
  </back>
  <!-- ##markdown-source:
H4sIAAAAAAAAA71d63Ybx5H+30/Ry/ywuAFgkpJ8gbz20hIda1e3mHJyHB8f
YQg0wAkHM/D0gBAcJ8+yz7JPtvVVVff0DABJdE6WJyciZ6Zv1XX9qro9HA7N
7+z5wpXN8LLJlquxPdGf4XLt3fBT9/DT4exk+nD48LP7p59kn5+dnZx9Qm2+
c+XM1WN7U2fLWbUph/V8amd1Nm+Gvlg3/mY7vK6WebkYrvKFq8rh7dnw5MFo
ObNffsBnN/Xo7bKgYcIP/XWGEYb0we39D+7BDqsP+PbQUI1729A/1w11dNde
8lmZN/4DmjVvG2pGxG/WfmyfvXx8/sw++e78m9c0sv3+xeX3Xz9/+vr1xZOR
fX3tLLWwtbvNfV6VAztdN3ZeV0vbXLtk7FXlGzejb+9bXsKqWHt8Yh9/e/H4
v589vXyNbvLGLT11Nq3qGX2dl0kPs2rqP85dM/+4rBrnP55eu+lNkfuGGg6z
1arI3Yz2cmSfNvY685a+slfOpV349dUybzCPpuLBn168/mZkmrwp3Ngefcuk
sK+YFPa58z5bOPuqrppqWhUD+ydXY432bGyfuMbV9HXW0AM/sH9cO6+/ZuXM
Xl5nNY3yuCqx2COTXV0RhXaGuD07MrSsMlvS8O/dFjPNGreo6u2YCDOvDK/G
Y0bNduXwcOZWEIGyMfmK5KCp1745Ozn5/OTMzKjt2EJQhqenw9OHhmZz39y4
7YZIPbY/ztIFDezPuh4sx29cTfsqa7HeLZY0wk/GN7TSN1lRldTx1nmzyqkf
ItXA+qpuajcnYvjtEr/8ZLJ1c13VY2PtkCZKXHV0PrKXstgjg80RKhydl7Pa
bbqvqnqRlfkvPDf65Gm7UHnvllle0Asl3sOHDx785wLPRtNqeWRMWdVLanzr
MP7T4ZPRXiqPua+7MsOpTKFdH36G71oNi+JeEqSbdMJPvKtz57HdoeuntA11
6ZrhE/DLO9nGmCHJa3blmzqbNsa8vs49xGiNDbR+5ab5nHq3t4GvbTVnseiu
fSlrNytd+6gVBEsdZqXNZrMcewOxCp2dmnvvmNrxgOUzI1lfFdnU8YzmVU0a
YGwd9bFNOtIJ2BvnVt5ChS0d8UO5EGFrp0/zgFKpnQuT9vwFsSh1Mr2mRn5p
eZ6rsNY4jHVv8cXCjUApFxdFXdT0l+1ISOh/YK+2dnOdT6+5s3pdlq4mDVcU
3uBB0Dg1fZQ1NHcahehOS8jsX6srEGxWkZqipTvuAQ+pF//IZiYI4Z7BsjDU
5rryzhbVNCN7QBvKa1lm0+uc3m5JZZRMZxZiahW7JCq6Ym4zfwOK0dTaNyVp
6mxGEyiNttszfrm1rsyuCtJy11VBZjfQ04vq825au8Zge4nFHvE29FQI1EO+
KOnjeZ3JE3QiayHt0jjDMyPuvXWF3eQNE9n3Njc8T3aydn5dNNBDxhEpaJiZ
I4tDq2m/ruj/6o+oi2mzDuPR2u1t7jbEAR0Wv8qmN5usJuYifbIiBqB1j+x5
OqLsRgnWpfWV9GlmWsYMHIz5Un/rMpvPiQto6UTRJhVLdBuZRtafL1eFE/J0
PiUOzVZ4KLYsiGecFQywzsuvVyvSyaRz5iRsSrNsZ/4DMKiM7hP5I54UUgfe
7VOadtK9JUIWW2Io5Wb2DYipc1jiSIqSDFiTiwihx7IiW03Uus5u3CNeRtzb
aVaTFpjcTgbolFyBOKqIfbuzGeZEL4KIkf/gSNl7FWQyFkW1ZYoxPZc0g1va
7VTx5eKMEIdCWeZgSiHJmPbRL7OiIDb3zXvEDd3MXJFfuZr6L7Ym6AzyUvKp
yACtCjqXFk78uFiDK5YVNWq16qktHHG8p52ApIU9ZEsrOycKMpVl2x2pnZEo
ABXkVHMXroEuhQYYiaFY5rNZ4Qz5S2Rj6mq2nqL3VhROPwL/05YGRclU21Rx
y4hWQaKhxqqrvxK38KqJhvJc+EVfDZQaMxII6ZFUNQQI2uWK3BlS8eJiCgk+
8pHmnkU1EoxUjuFNGWNJ9FwMG+sjGpj82FqED0/m6xqyT+Kj7pNlVxLKx4CU
l44Xbk8fDGCSyCEFY7FkiwBkkerEL/N8sa7lyQJMR11AGhz5wU69QVKCED5Y
SveW5jetZjKbat2s1o0uUSizzKC0wflNuu5qRVtLQ5ARdRAHvJxUZNYL90bf
TWgfllcQ4qt1I5ojtKJ9wkKIvBiVvPNfXGlFQ9iUu8a2Y7OMuNF2k22hZIhT
UguiRkuWqq7iLO1SWpukNRiYpkXSxKIJO73IVphcUVSbvjWfFiRrXuSc2R7N
ldfGxpwK3VoLq7bOO9elXbppraWFO0WfQN8Gqw2S7ZjnObmR5M9duWlGwSf3
fFW9JZKig+uKNhuPZjktD2Smr9kxqWqhJbmB3BNeMP2pzZrIvajskHvokNjT
P74icWho0KblCjKl67r0suKOI4I+gnW5Fzj3k2NRaLQetmvQfQOYpWZn12gj
zkCDXc0X6Ok8yRV1MrJ/ZoWekQCROgx8Qw4E5gBpELXI2kwYjRwDr8tYkW3I
S1qiKKupRosZ2nZ1V8I9VYlW3GCeER1k/X23CF3EpX96HFVsk36b8OWmWhfk
tZCKxewRZja8hGpT6uTVokbWalm76xC1w352jB7SkWXJ8Bwgr1ExiuYjqt8f
2Yueb8Jhc2ZXWU0msrCrfAq91Wdz4m/PeoRHpPn6R+nq+DUkBVwHYaOIZkmd
PO45Xx2qnZ4cs5ebOHA1cc2MQk2ZN1FghZBryFsS/TUm21ydJ1F1ma/gmgv3
1Vhcx6pfkd8FbofzVwU5bBcnhMCWl5gsS46CCa1Apy4bbw366HwBN41oAJeJ
lyOuAX2ypQ2gmOo2GFLsAHuC6KLjTcY50V797nfE+xWzLZGbOzPmgo1w4IS8
7DlntENenLMl2TTekegwCH8ZL9ShmZGokea/oW6Ux9mqOL/bLRYTw1l4RSRU
eJ7POaCi76Hpx1A00W/MVALY94FjkaVT4ThlU1e0Zzwh2s9Mx2chJCO5Bq7m
m6qadTxNosw//vGPGNOmP08uHj+9fPryxe7TJxdP7Nc/7G003P3Z/3Rva5jz
Bnq3dnNoavBOyhYDtXh7G+//6foO4ErSEXdov+Nh3Ls9PTZ7OwgMytPe5KRg
bW/2orn3NqYNuaJYbItYsv2JOt7e65iMAzPIusoyPC1jnCe6j6ayt3nXaIQf
Yss8hJ/CzaSM9g8vmpVtCHnOe7+JFjXOtH0eybQN+nx3iHnjxCzPKMAlO82r
DM48W5h3bA6icnIIiYg0v/6oWQGd9ugOvEFGP0TlM4632OM4vO6oD7vUaE0U
NNcdxu/pSzYOd2iukTIrAOjHr3dCZHKEmq14/4hTs24wQe4de/zs/bSOvKrT
NLg+C6z1/PvL1yabTt2qSVrE4BSvA0lpcUtR5Tuh6sikXUf17cU9YvO2uXYi
A9UKgVwlzoiKQRLVB6Wq82ut6enxQHEn6o0DByLw1NXAkgz7lWi2yXyEYURR
UP+WdW0nMi84kk1gAftuWIC1R02xBTE4jDVF/BpDqk9IWoJkdGS/c1mR/wJj
HeGkWeUEOVfEICHV0AQfONmxloK8TPg/MDBssxEIEe0Sz9lEgpKj6+EADAUf
aFjP1HVVCyrg3IwZI8axYzGYkQJzEkLBZTqYYzDfcVMGgWq0SrOHachfQZS5
h016XpdgLeYdWAsxyGxV5WWknfpl8TFWCioZ8ToRE6HTAX4LuIiTyAG6oawo
KnbKIa2pvYxTund7dnxAOr/jxUdx/vX98vxr+jFY9N7tf5zGOB0eLGu44/7H
e6xz9+fLX3/zNFTTzFP3loh4e8Zbt/fjjtQGwwVMed/HHziNLvBLdOmRPfn4
i/eSo9NzNGO7nf6TPasePNDv/9sOavja4SUW0X0f7+DDFL40pADcbIfr7kiN
O81Zfna57nR88OMS3n3IJ5xZeBb+4MfZFeIBVpfXHFQNlJ0P8XMKtwWY9eDH
e9IZ/LHYaVL5P6/zWs3GMwUgBSa9oeAIyUBvj2BKjwbyr33xkn//7uKP3z/9
7uIJfr/89vzZs/iL0S8uv335/bMn7W9ty8cvnz+/ePFEGtNT23lkjp6f/3Ak
VDh6+eo1hQ3nz472hz4NkiUAEly9qh0A9MwbismmdX7FCWP79eNX//s/pw/s
3/72b9998/js9PTzv/9d//js9NMH9AfMe2Kf5U/EhgbbkdXoBYDvNFvlTVZ4
Vn/+GvAAABBSxf/+Iyjz09h+cTVdnT74Uh9gwZ2HgWadh0yz3Sc7jYWIex7t
GSZSs/O8R+nufM9/6Pwd6J48/OIrdpGHp5999aUB87xmNVgV1WIrLAO9yDmb
d2T6iPYHM660GUjcA2Vo/Vg13EYB4EE3ozQAn77JZy0kExwQQT8ZKwKKhbBW
wJNuymTmx8Z00vfjri9MfDVsQ6eIn2GZmmAwe3J4Mp/N9Raua9diSI5UsdiB
IrFmF9ZIEl/cGU2crNh2EADbbpYQLp1Xbwm6hCswIA8IctgTJ0YNZQnjfnTX
G3RPKoNRMsMo2WrdsEuSAnwKJ2qy0CauYYoC5t5kt1leZJwwE5h7TtsCx8ZX
82bDqVXkIAVXYv+PA1csUbCd1iVHlPSSMW9JtCSoIRxkNnlJDkIQOJo4tHNb
0JCjbgD5AU2+ZU1MtBI94tta5huCXtnFbZLszJQxjTBmF0yHX7mVAgzPFSnR
sWaKihqDSwuwb6tQbVudIls8si/LCDkq+PQI2wAOqWoMXJUhLscEgwEFV8QB
byvw0yLLgXWX+rURpklDz4SXQmgW414i77M0TB5rFB1ApHbpQLG8bFcb4VL4
ZCQ0UJq3+8E5HQnGR/aim9cSCNg9AofAf5fJaXIswbDW5TKbQS8/0Z5keoAa
0ox1BG9pUzRSYbbmVCxvRuwxl+hMHHUy2EjSRNrJboVQR0AFQA4RVNCQZpb7
aYY6pkfojySkWrp2j+aaIeC4PgxsEkCZ1tPDbFvehvQV86EaPgQwAZJt4Vhi
kIjGBvhWw46oM4k6EI4Il8aYCAJLb03MlHtJ1m0xFrMM17tEgQmRPuDncohg
17SS1MGZsSzawtKuMs8Zw66ybFIcLA/JG5k3RV1TigwNPEjaElI+Ux5kDFab
i7lQ96qn4zbEUTQ1JAZppsjzwYOghyhDacdAkmZdO65NuRYQu1PCwYkDcsAs
8iavd9Xoqiry6VYtkKQBUI3ioTRgV2iTKSJ/JIIfQsjwNeu5uPy2nQLJSXJn
xMaYProIniHj/H8oMtBdAsU2TDz4kwSJH+wj04enI40PT/dHn/rhB4QVVjK1
2wRnpV4F8Tj+4HlZtqiqkHqZsTst7Gy0E+p1gif65OWLZz8EqD2z08jHAol+
SFjS9hGiU2zsCJjRnSf8AaRJzH5W516Y8g7tu6iu2g59d3+UBrC7ceavdyBK
1J2ku2qFb+9CigejNuTdG0lHKFrVdgpFfxiv5pLOCtk9BLaP7kDJPPEBRGrv
0HgjqWkpKvhX8EmkP7jZaZlUWd2F09T96sLp/4KpKhn2qIqHoxZwOLW/jzhC
4IcPZ8g7zBt6uFxL6BFSqKheZh9xnteeC9hKr5mgUPdIZLoh13k1NjsmUAxp
FC2K1EIJHDGty7l2hUfQ3Gfr2by4+NPFd6hAArraxjC0p00n7TEKcMDjarmk
D74hBWoO4eKZ/a/Lly9CNU+o2OF5xiodcaND+nsHzvdIy9CWwefhX2IipyFn
oxHfBoppmdU3TjDgRbaCr3QLJwL1Pu+JMqN1HJiYwg2LQHm0wAlszaUqKdb5
eGpjP5X47TNBcShs6ZXJitHuJQSfnz/WugkplYJjEesQpCdG26Un6WHl6iHM
J4VA9Xalrdh9jD7SJ1ar2UMdwob8AKcb8CjGvVPZuxD29oqXPh/APSrWvDtc
RCduMG3oWfQ9Y1a+u2T1SDjpoLV0dViLarCYfNibe3BC4li4Gz1Hmoj9D3vG
iEoKuTMoxeVoTfVImEk60fhZ1lvXoZ5MCkPgw2VTretpNuR5JjWNZyYtuuzU
OuqSZMs9HxrxNgA4/GBv8SZYnmQJ9QtaCLPbZ+qymuCyei20kzgrLcJrC1lr
LjgmIvi478gUkWs54Tj2TVNN2gqctqSRPlAZ9FJBIMGJdGUiRkKOLaqWYp6H
PNWCi8IkFRLkcaDGDYtBxNUrIfCOwlWunOQEG0I5iJYCE9AHYG1dM4r3yElu
ZwMGgMKmnbwVoCY9Q8Gb8XN7jEKjttoZTczRMNdZMZfQO8SrUioHxk/JdK75
ZtXHxr1F0rCPgySlmG1jlUYk+oU/2ipo6MLeFiUFeigeUirfq6TYICultCQi
Wf1G8ANKVxwPJGG2U0eOSAy8MwrVJrtMiXMGvg2YmjbTeG9CT97ks8kxmwld
lE3DssnSL/iLQac2dUKmau1mb7Jm0i+9RdJwReaFq3YLDjy5dk9ZCMGfdxL6
5it2KEgvxdZSltJOIE/O+mDaHa19zaXEjsjPsVkoMCTmX1PPUy7XxmGmiiJb
EuO8oG4Lht+iMHLGmIOodEmhugv2Z0NbU21ENjvpwTFzASynkW9awHG+FguA
dSPiAsu0bdsk8OjU3rt/cqIwjQ8WaBcBO96ZNC+rjdMNRbttsZDMZ2Sf9vvD
X/upaySrHJfNXLPKprGWFMwTdm8AGhOzERNqB95oQDzoOyeFmzcK2zGvM8vK
2DATcXxFfbrWhBszd5Mr0oFkYXl2QNSO6CR1jYfh0cEOnNAP3A6BkoYdE3AF
+23E56hM4+Rsxr8GDzngDj6Us5MmyfJ6YJilkghRSojKUO/lnR4TUMruwMam
Axt3MUStcNJ1addNS3RGgo0gU2mlp6aQef4QrzB3XZdM/SuTeLf68/vhEGuj
QEjMY8BH7rULPD7QbBuqoDvF9jvBb7eoSEQt99F+htiHzVWvTOXX3t+/j9OU
oruUqOz37gPoUyd3HCn1N3t0ezQmh0WGOIK5o7+POu2PwlvRt3hPvw1PP40v
RM1yw1HvVdRLeKsnv4Znp69PTsb8v7/EL5nUb0DqIxzjKLwLb8ThQAcAsGKD
zfUWz1jop3W+alo+9/Zj5etgaCNvMdx0ZP8upILDpqIHd2tBDHU2shPQgV9M
OpQg0xuMDtucYF/YEPtsnqonPyZlSar49Owz2EE4cjDZMIRm8uP58C/Z8JeT
4eejN8OfJgdTB1Ke3w6DCY0mJh4uZamfDfjkWMDzxJtO9WTZ6tYiX0IhpeaC
Vvn968dy5AQCy4L/F1ppuyETKf2mLcGxrVYm1BtUl4F0ILgS8ygr2ztwyadV
tyZ8AM6VpABCOVatGxJqGlU2W4iP7Z7EciWzR64x68m6vCnJ9E9CFqXd7Kt1
E+XeAPEmeVtVNFnYeVHVqPzwldW6q4lisNhp4i+eRmYoAuJJz2VLH56cJFvK
qguWOmuy8DuOpORt4OSDXekaQXjjrIeD+1xu9UhPiOJAhB+/ffn86Ys/DF89
/cPFyxc/9WT7C+GNL4WHTBXbaZJItpVjMU4m9/0A+jRaftMGbfD4tKuOwQ2s
yBBtyL5B47SHdTStktm9Ze87xemZSRJqBwVBbAmXIcR0ma7DpAp3EMqXJCrx
oWhYXFyp7sZIEW42XMyGRpp547f99FvrHEnMcpPzQTczgd4m0r9k36CNWjyj
GnIkhCixyWdcuc7ZC2h4sobt6cfIrQxs9HGN4NcGbCNYQ80WSTkoauzEaIYg
7L0qPgx/F+3+82/X7mH6b8hbpI9PH4YXcR7Uw5+ZOdgwssO2nkIWpQ6RnuGE
2lexR2abNwrEobWKbqvbg9o86JgyR/88mti+QjX+uqobBwGKxZLQIcq+rPvw
jNWpniqKLaC0jZzlzew1ssdaOiOdy2CZNKBIYoHcjX4RdDcf7ey5u+QRbn2r
zHVwYcwN6dt8zstrdBivDCLnAyqkHyfpJohqk/p6mD2O0E6g3u6f0KdhW+Qz
VAAN3XLVkIqPujBrzBJnBvvqcNLZmcMdGK7Xpw4+edBpf0AFMHO3+vn9ijIK
WKIjL0krchaNrHcCUUmaHozS4mzJUdq+JjQdNSjROBL0AafUU8H93Px7Mu4m
65aCHM64kz/L8+ZK7ZKi2mojcExmcWEENgfVTsQEnaJdrfnsjCHOj6HfeXVZ
kR5IDHkRnPcedLPuKGHlSBOvjEb2mFx7YHrFZyxderDo/WpJvruLUspGO2op
EPyfV1s6HfoMKXMWftVKrZpJRovOZJL+j7xiewrJHFBIWauQOufWoRWiktEu
JMjP1CJiU+DbTGTav0F2U1fmPC1MZ2clpCbyZmBiSfqOFzPTeuRY5vF+UVW5
+U2CSt3vlpEc1CIa8AvQgexFQL84yLfdzZRqATGrTRXucuBDTOfUutAD/DHu
jpUFYTJBWqrpdL0SiMAXFZ/chyNdZx5gK3VEfjAAySBwsB5aCFOHzqRIwwra
YsK1JQLhbd9RupEmRgZwWtIKjTBGrAzplDL0gvJq5UoTDJnG5J0ynJEAHZpq
Cy6TVNY8CQdQEvUiXt1OZnuAXCYtqvW6YnWT6b0pbVFVNz5UVikV5Hxp19wZ
cq5W3sUzpjybd7sGJxo8GlzHId4nRgtIyCbLdSd3juCH+3nYxYVixrfJ4YMG
9ZcZylFvQiHWNFthzPsnusO+1ZVJwVAocWGHJF+5A6BESwpoALUdYNiZQCHC
IJ0K2wReCnTbrcDdU5TLaETVCqAmJePxa05Yvneah1n2wyfBPlGanQ1RF1h8
mOT2O035J0z6yrF3lR+acCz52j1J1EdpDs5KjqLzQajXwbcMt6IM9h+PGYS0
KGl6zW2epzusyf4Y/244RuYzbY0cUYl7u6ywUJMKFX/uGWpks9OVG32IHdZ6
PPJUFjX04Dw9BD5FxpdYmedB3C7Yed0RX9WZldS4AT+UBAF0GxILbQFBtUax
For6SEP3JySyT0tbcU2mxj++qVaeYfZeAzndxNI/U3mVpJh0Im5yw3V9MKmY
Y9DDjK2zY86SShtZLqRd2U04c/At3ruoBZ0apyh52AaZQ9Z3FLIlUk6RYCxO
IMN80hKBu0jr8vRo70xNBibLegXRPncPBZ3wQ1hs4+JtQBsu/MZWhatzkJIG
z8gR+P1Wc6AjklxgQD4mWHTuF0kyrZnWgIaCyNRtNFz+EsF0rQHFGW6UEPCB
rMASHb4hq7WpUe4VzhbHzxLWFsKz2o1ahJFyuVwAlaWkZDm3wbOcE19fO022
KowOVFXcPCQbjVxEEo5uZmzhXuw92Cik6wo6e1/qc2ldgemoxT05jtb+pPbC
FaGEU5DOQUQs5ZhAHS9kiBdwjKT+QUz9ZTgUb877p1AwSwh3LLAMh1ICpdt7
csK1Qy155YmmB7U6ENJWu6t1Xqgx1IMxxmt2kN/NgohxJgge1WU8FYOD2dWG
l9vzC9pIovUNujTXShLcI9IJNmi1Gg3cP+OCyZpzFNfubeL/Rrf/ipFl8VLi
Q4A+h8FxvgjvvXB0GzXIhNRFn6MYMgkwYQdy4n7ZAz68uZDbkyZX2wn73hNM
R5FnZjEvfv3ekHqC2e2AmeHjfhDwGuyRhgGKWpro70fOY12qfMPgRB/yRLU7
iS0DdbH5lQuuTKZQGu48y8p8DiwkwcOmRaYXRCTBEloIl/TQ+UEMfAZ9EGJg
JhDfN/E9k5Dc+QZoDVLq3YIkybtTPKDSMkF9d7aNl4DB4lEgvXJ6y4NWQrXF
iOpz4ViNmJWY2eN7luZ8p9O9MIFBOJgwsK+2zXV62czM3eZTN6QIyxk5dMBW
HqA7Uf24t1viXjMy5LVUGNn5AMmq3dPI3I/7yodfG9rDcsplEKL/iCMLBrGQ
r1s3iwr8E7ZdtMRS9DjgpKlcrtceSOiOESFwYZV1zSDGbVbkuB3Qy3EI5dd7
mX0ftx5L2VEQJ9pnEhDdXpGQtoCIs/NhfpFt+cIJWKY905kFH6QF3JSsSmmt
x2tw8wZfBpJ3Efag55FnEgDvdGQiUwW0IPJWqOgTqeOuNQ+r9dqVwRU6Fc9D
igmwONb1F4yAs3fXvd2tms+TG3fi6VE2ijAzAZiKe2SSaBkFGnPc6HPjtuHQ
MBe2bSp7VVUFR0acqiqyBcdhBtZEEfixnQyHoRJ8eHsmITU9S/B4CB85Nlpo
kBl01OoAmH0nuSe9O0svpWIXpFXx5HsJNduk6qFEb5jPm1u5F61e94OMBHhb
ApFnnHW3inHQa8ZYfzfrIUmFQVJScDAUAkHeSOHXwUmFxEa4cCItf07drG7L
ANtoAVNaOZdZ5A0PRTsSdfQCmz1OH/afSxtnXGQhc5HCFbV2yfIi15NHjnsq
tYQhL0MYb1/lcsktX69EBmsHFH2Vv/MIEgo75LOPvIm+GTWKXxDb1tis0m1s
DacdBSPxfk7W8HK/Y8gN6yGQETLGZ28ChOu57BALvpL4SYAC0ZpAYHcRXBMm
/GeN1Vhh9FDbQTgsgcv4IHh8bZpq7bQGsC0BTYsJuEhRj3GQIqEOTN7WZvBY
YOsr4Qheuto1+jTlDgmHEPKs6jwWTnKGI9FxmLR4qPT3ox6yGe4ek3ITWZHU
dMnhJ7RGjLPVa4rEqCLx6+WCtBlOv1xVsy7t3+ykMnqoaxuZ/Skr1rArWmJ0
MhpR9AWOJediuWIolW0YjoLJeeIOQOSpBdTr12kdzKVgmT7VtFEa4jVqoUVa
P8V2kh11VNOZtr74nQDpRMvQ2vNloXKKCxSDrxAA5sHB8l+t9kXUGQ3xLPer
rCGX38cbP9KyR6m5A+1q8WRi3anEPedx4t0S2iX6FELQ7gEI56oKcV4jEu61
mtbNAky8c59hD/7txiRpfbLap/dnsbGKfnZQFzGyOL1VN+pUCfo7k4pYNj9c
/iDvteZKvxkdrDAXcFiJJfcfkU2HSyBhMMMJpyaG8ZEi9HmQ6Q6sGKqLklpg
0r4+ZYxEEYcNEY2g6HXar0muf0lWgOKJNoPeVeGcJY/mZvf63c7ADDF0kxmY
ncATWkOqdXWpfx3KTXF5mBAmIF56iVhI1WM7F6iXTJJdH3m94+t4bHesD3vD
cpIzC5QwEYzky4YCwmK7+j5q6nYku2C/VVJgUNYfJYZxn04WjII4Sjefz8pp
FbXcliPWnaGfvGRf1KT1FV0uYVon1ndvpZ00Sb+CTqNFrPnE4GMVcClVTrUa
R28zL3aWocsF26syvYohGGPcBS4HB3ePEe9JaoopZFskhxDl9qDEy5RuBLNW
zKjTc79LE/Kj6HOHK6Xj6ABPr6vKB8gKdaFGKBlSqlKuz9ZqFizzSNzsoLLn
TlQV8KmWpwSH0aj3kUZx0Zx09Ve4xWLQ3hE76qG7en2QnEjVW+I5HbUuO8la
TX2Z5DavWLk+S0CbAKAcuIkpYEZNDwWIAV8s25I5wOcNtQcKT7VMGuGBNqDV
T8IlRj7QBKB4HuHwvVm9QXvZ0qaK0uoVsYM/YxmYbjrnT6P+m/2V3JppxDkl
ZA/pP4bLN3nJiKwkxfjosKBUbepPK8nLNiXWy3Omx6SnmRRvV926/HI3CSSl
2B1c2B7AhYFzkpmi1vHGK87GZ6bAkW+5FsA7CVm0B5ZbV1brxXVA5fO6Pd1U
JXfyxnniCHLvXlBcSBWvIkiqqdiJZTuY8e2iGnGkhkbdT8YwRBsGV11vmWC2
gqrQK/BF+3eCFV5gid5WfPoCVzmfvzjfUV/dOzHCAeSyYn+fW9RuQYq83qoh
SQ5SebOLKsViGAUWOihSQGLJS24P1QzYVQn+Mp9qAdnBurGspPNfIYheVftf
IXidKoruHLn3VGHwBdfYHfN/15/g+F9mAAA=

-->

</rfc>
