rfc9171v6.txt		rfc9171.txt
	skipping to change at line 1041 ¶		skipping to change at line 1041 ¶
	4.2.5.2. Node ID		4.2.5.2. Node ID
	For many purposes of the Bundle Protocol, it is important to identify		For many purposes of the Bundle Protocol, it is important to identify
	the node that is operative in some context.		the node that is operative in some context.
	As discussed in Section 3.1, nodes are distinct from endpoints;		As discussed in Section 3.1, nodes are distinct from endpoints;
	specifically, an endpoint is a set of zero or more nodes. But rather		specifically, an endpoint is a set of zero or more nodes. But rather
	than define a separate namespace for node identifiers, we instead use		than define a separate namespace for node identifiers, we instead use
	endpoint identifiers to identify nodes as discussed in Section 3.2.		endpoint identifiers to identify nodes as discussed in Section 3.2.
	The EID of any singleton endpoint may serve as a "node ID"		Formally:
	identifying the node that is the sole member of that endpoint.
			* Every node is, by definition, permanently registered in the
			singleton endpoint at which administrative records are delivered
			to its application agent's administrative element, termed the
			node's "administrative endpoint".
			* As such, the EID of a node's administrative endpoint SHALL
			uniquely identify that node.
			* The EID of any singleton endpoint is allowed to serve as a "node
			ID" identifying the node that is the sole member of that endpoint.
	4.2.6. DTN Time		4.2.6. DTN Time
	A DTN time is an unsigned integer indicating the number of		A DTN time is an unsigned integer indicating the number of
	milliseconds that have elapsed since the DTN Epoch, 2000-01-01		milliseconds that have elapsed since the DTN Epoch, 2000-01-01
	00:00:00 +0000 (UTC). DTN time is not affected by leap seconds.		00:00:00 +0000 (UTC). DTN time is not affected by leap seconds.
	Each DTN time SHALL be represented as a CBOR unsigned integer item.		Each DTN time SHALL be represented as a CBOR unsigned integer item.
	Implementers need to be aware that DTN time values conveyed in CBOR		Implementers need to be aware that DTN time values conveyed in CBOR
	encoding in bundles will nearly always exceed (2^32 - 1); the manner		encoding in bundles will nearly always exceed (2^32 - 1); the manner
	skipping to change at line 2444 ¶		skipping to change at line 2454 ¶
	Change controller: IETF (iesg@ietf.org)		Change controller: IETF (iesg@ietf.org)
	Reference: [RFC9171]		Reference: [RFC9171]
	10. References		10. References
	10.1. Normative References		10.1. Normative References
	[BPSEC] Birrane, III, E. and K. McKeever, "Bundle Protocol		[BPSEC] Birrane, III, E. and K. McKeever, "Bundle Protocol
	Security Specification", RFC 9172, DOI 10.17487/RFC9172,		Security (BPSec)", RFC 9172, DOI 10.17487/RFC9172, January
	January 2022, <https://www.rfc-editor.org/info/rfc9172>.		2022, <https://www.rfc-editor.org/info/rfc9172>.
	[CRC16] ITU-T, "X.25: Interface between Data Terminal Equipment		[CRC16] ITU-T, "X.25: Interface between Data Terminal Equipment
	(DTE) and Data Circuit-terminating Equipment (DCE) for		(DTE) and Data Circuit-terminating Equipment (DCE) for
	terminals operating in the packet mode and connected to		terminals operating in the packet mode and connected to
	public data networks by dedicated circuit", p. 9,		public data networks by dedicated circuit", p. 9,
	Section 2.2.7.4, ITU-T Recommendation X.25, October 1996,		Section 2.2.7.4, ITU-T Recommendation X.25, October 1996,
	<https://www.itu.int/rec/T-REC-X.25-199610-I/>.		<https://www.itu.int/rec/T-REC-X.25-199610-I/>.
	[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate		[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
	Requirement Levels", BCP 14, RFC 2119,		Requirement Levels", BCP 14, RFC 2119,
End of changes. 2 change blocks.
	4 lines changed or deleted		14 lines changed or added
This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/