5.1. Primary Block
The fields of the encapsulating bundle's primary block (Section 4.3.1 of [RFC9171]) are populated as for any newly created bundle, subject to the following:¶
- Destination EID:
-
SHALL be the decapsulation endpoint ID toward which the encapsulated bundle is being forwarded. When the payload is a segment payload, every encapsulating bundle of the transfer SHALL bear the same destination EID: the destination is one element of the scope that identifies the transfer (Section 4.3).¶
- Source node ID:
-
Set as for any newly created bundle (Section 4.2.5.2 of [RFC9171]), except that the source EID MUST NOT identify the null endpoint (dtn:none, ipn:0.0, or ipn:0.0.0; Section 5.2 of [RFC9758]): anonymous sourcing defeats the peer authorization measures described in Section 7, and disables the status reporting described in Section 6.1 (Section 4.2.3 of [RFC9171]); Section 7.2 describes an alternative for deployments requiring sender anonymity. When the payload is a segment payload, every encapsulating bundle of the transfer SHALL bear the same source EID, which is one element of the scope that identifies the transfer (Section 4.3).¶
- Report-to EID:
-
Set according to the policy of the encapsulating node.¶
- Bundle processing control flags:
-
Set according to the policy of the encapsulating node; the flags of the encapsulated bundle have no bearing on them. The "bundle's payload is an administrative record" flag MUST NOT be set.¶
- Creation timestamp:
-
Set as for any newly created bundle (Section 4.2.7 of [RFC9171]); it is unrelated to the creation timestamp of the encapsulated bundle.¶
- Lifetime:
-
SHALL NOT exceed the remaining lifetime of the encapsulated bundle — its lifetime less its age, determined as specified in Section 5.5 of [RFC9171] — at the creation of the encapsulating bundle, so that the encapsulating bundle expires no later than the encapsulated bundle. An encapsulating bundle that outlived the encapsulated bundle would waste network resources carrying a bundle already expired at decapsulation, and this bound underpins the transfer machinery of Section 4.3 and Section 4.6. If the remaining lifetime of the encapsulated bundle cannot be determined, forwarding by encapsulation has failed (Section 4.1). Where the age of the encapsulated bundle is determined from its creation timestamp, the tunnel thus cannot extend its transmission opportunity; where it is carried in a Bundle Age block, the same holds only if the decapsulating BPA accounts for the tunnel transit time in that block (Section 5.2). The lifetime MAY be shorter, deliberately curtailing the tunnel transit: for example, where it is known that a bundle failing to complete the tunnel sub-path within a certain duration cannot achieve onward delivery within its own lifetime.¶
For a segmented transfer, the encapsulating node SHALL set the lifetimes of the transfer's encapsulating bundles such that all of them expire at a single time — the transfer's expiry — regardless of when each is created: each encapsulating bundle is created with its natural creation timestamp, and its lifetime is set to the interval remaining between its creation and the transfer's expiry. A node without an accurate clock measures that interval against locally elapsed time, and carries a Bundle Age block as usual (Section 4.4.2 of [RFC9171]). At the decapsulating node, the expiry of each encapsulating bundle is determined as for any other bundle (Section 5.5 of [RFC9171]); where it is determined from Bundle Age blocks, the encapsulating bundles of one transfer may present differing expiry, and the earliest governs (Section 4.6).¶
Assigning every encapsulating bundle of a transfer an identical creation timestamp, and hence an identical lifetime, is not an alternative. The creation timestamp is a property of the BPA's timestamp mechanism (Section 4.2.7 of [RFC9171]), not a per-transfer parameter, and together with the source EID it identifies a bundle: bundle status reports identify their subject bundle by exactly that pair (Section 6.1.1 of [RFC9171]), so encapsulating bundles sharing a creation timestamp would render the per-segment delivery reports of Section 6.1 indistinguishable.¶
Selection of all other parameters governing the forwarding of encapsulating bundles (priority, security policy, etc.) is likewise a matter for the encapsulating node; the corresponding parameters of the encapsulated bundle MAY be consulted where they are known.¶