Diff: rfc9675v2.txt - rfc9675.txt

	rfc9675v2.txt	rfc9675.txt

	Internet Engineering Task Force (IETF) E. Birrane, III	Internet Engineering Task Force (IETF) E. Birrane, III
	Request for Comments: 9675 S. Heiner	Request for Comments: 9675 S. Heiner
	Category: Informational E. Annis	Category: Informational E. Annis
	ISSN: 2070-1721 JHU/APL	ISSN: 2070-1721 JHU/APL

	October 2024	November 2024

	Delay-Tolerant Networking Management Architecture (DTNMA)	Delay-Tolerant Networking Management Architecture (DTNMA)

	Abstract	Abstract

	The Delay-Tolerant Networking (DTN) architecture describes a type of	The Delay-Tolerant Networking (DTN) architecture describes a type of
	challenged network in which communications may be significantly	challenged network in which communications may be significantly
	affected by long signal propagation delays, frequent link	affected by long signal propagation delays, frequent link
	disruptions, or both. The unique characteristics of this environment	disruptions, or both. The unique characteristics of this environment
	require a unique approach to network management that supports	require a unique approach to network management that supports

	skipping to change at line 2205 ¶	skipping to change at line 2205 ¶
	Reports are transmitted by each DA when produced (step 2).	Reports are transmitted by each DA when produced (step 2).

	At a later time, DM A sends an additional policy to DA B, requesting	At a later time, DM A sends an additional policy to DA B, requesting
	the production of a report for EDD2 every second (step 3). This	the production of a report for EDD2 every second (step 3). This
	policy is added to DA B's rule database.	policy is added to DA B's rule database.

	Following this policy update, DA A will continue to produce EDD1, and	Following this policy update, DA A will continue to produce EDD1, and
	DA B will produce both EDD1 and EDD2 (step 4). However, DA B may	DA B will produce both EDD1 and EDD2 (step 4). However, DA B may
	provide these values to the DM in a single report rather than as two	provide these values to the DM in a single report rather than as two
	independent reports. In this way, there is no direct mapping between	independent reports. In this way, there is no direct mapping between

	the consolidated reports sent by DA B (step 4) and the two different	the consolidated reports sent by DA B (from step 4 onwards) and the
	policies sent to DA B that caused that report to be generated (steps	two different policies sent to DA B (steps 1 and 3) that produce the
	1 and 3).	information included in those consolidated reports.

	10.5. Multiple Administrative Domains	10.5. Multiple Administrative Domains

	The managed applications on a DA may be controlled by different	The managed applications on a DA may be controlled by different
	administrative entities in a network. The DTNMA allows DAs to	administrative entities in a network. The DTNMA allows DAs to
	communicate with multiple DMs in the network, such as in cases where	communicate with multiple DMs in the network, such as in cases where
	there is one DM per administrative domain.	there is one DM per administrative domain.

	Whenever a DM sends a policy expression to a DA, that policy	Whenever a DM sends a policy expression to a DA, that policy
	expression may be associated with authorization information. One	expression may be associated with authorization information. One

	skipping to change at line 2406 ¶	skipping to change at line 2406 ¶

	[ASN.1] ITU-T, "Information technology - Abstract Syntax Notation	[ASN.1] ITU-T, "Information technology - Abstract Syntax Notation
	One (ASN.1): Specification of basic notation", ITU-T	One (ASN.1): Specification of basic notation", ITU-T
	Recommendation X.680, ISO/IEC 8824-1:2021, February 2021,	Recommendation X.680, ISO/IEC 8824-1:2021, February 2021,
	<https://www.itu.int/rec/T-REC-X.680>.	<https://www.itu.int/rec/T-REC-X.680>.

	[CORE-COMI]	[CORE-COMI]
	Veillette, M., Ed., van der Stok, P., Ed., Pelov, A., Ed.,	Veillette, M., Ed., van der Stok, P., Ed., Pelov, A., Ed.,
	Bierman, A., and C. Bormann, Ed., "CoAP Management	Bierman, A., and C. Bormann, Ed., "CoAP Management
	Interface (CORECONF)", Work in Progress, Internet-Draft,	Interface (CORECONF)", Work in Progress, Internet-Draft,

	draft-ietf-core-comi-18, 23 July 2024,	draft-ietf-core-comi-19, 3 November 2024,
	<https://datatracker.ietf.org/doc/html/draft-ietf-core-	<https://datatracker.ietf.org/doc/html/draft-ietf-core-

	comi-18>.	comi-19>.

	[DART] Tropf, B. T., Haque, M., Behrooz, N., and C. Krupiarz,	[DART] Tropf, B. T., Haque, M., Behrooz, N., and C. Krupiarz,
	"The DART Autonomy System", DOI 10.1109/SMC-	"The DART Autonomy System", DOI 10.1109/SMC-
	IT56444.2023.00020, August 2023,	IT56444.2023.00020, August 2023,
	<https://ieeexplore.ieee.org/abstract/document/10207457>.	<https://ieeexplore.ieee.org/abstract/document/10207457>.

	[gNMI] Borman, P., Hines, M., Lebsack, C., Morrow, C., Shaikh,	[gNMI] Borman, P., Hines, M., Lebsack, C., Morrow, C., Shaikh,
	A., Shakir, R., Li, W., and D. Loher, "gRPC Network	A., Shakir, R., Li, W., and D. Loher, "gRPC Network
	Management Interface (gNMI)", Version 10.0, May 2023,	Management Interface (gNMI)", Version 10.0, May 2023,
	<https://www.openconfig.net/docs/gnmi/gnmi-	<https://www.openconfig.net/docs/gnmi/gnmi-

	skipping to change at line 2642 ¶	skipping to change at line 2642 ¶
	Bormann, C., and M. Richardson, "YANG Schema Item	Bormann, C., and M. Richardson, "YANG Schema Item
	iDentifier (YANG SID)", RFC 9595, DOI 10.17487/RFC9595,	iDentifier (YANG SID)", RFC 9595, DOI 10.17487/RFC9595,
	July 2024, <https://www.rfc-editor.org/info/rfc9595>.	July 2024, <https://www.rfc-editor.org/info/rfc9595>.

	[xml-infoset]	[xml-infoset]
	Cowan, J., Ed. and R. Tobin, Ed., "XML Information Set	Cowan, J., Ed. and R. Tobin, Ed., "XML Information Set
	(Second Edition)", W3C Recommendation REC-xml-infoset-	(Second Edition)", W3C Recommendation REC-xml-infoset-
	20040204, February 2004,	20040204, February 2004,
	<https://www.w3.org/TR/2004/REC-xml-infoset-20040204/>.	<https://www.w3.org/TR/2004/REC-xml-infoset-20040204/>.


	[XPath] Clark, J., Ed. and S. DeRose, Ed., "XML Path Language	[XPath] Robie, J., Ed., Dyck, M., Ed., and J. Spiegel, Ed., "XML
	(XPath) Version 1.0", W3C Recommendation REC-xpath-	Path Language (XPath) 3.1", March 2017,
	19991116, November 1999,	<https://www.w3.org/TR/2017/REC-xpath-31-20170321/>.
	<https://www.w3.org/TR/1999/REC-xpath-19991116>.	Latest version available at
		<https://www.w3.org/TR/xpath-31/>.

	Acknowledgements	Acknowledgements

	Brian Sipos of the Johns Hopkins University Applied Physics	Brian Sipos of the Johns Hopkins University Applied Physics
	Laboratory (JHU/APL) provided excellent technical review of the DTNMA	Laboratory (JHU/APL) provided excellent technical review of the DTNMA
	concepts presented in this document and additional information	concepts presented in this document and additional information
	related to existing network management techniques.	related to existing network management techniques.

	Authors' Addresses	Authors' Addresses

	Edward J. Birrane, III	Edward J. Birrane, III
	The Johns Hopkins University Applied Physics Laboratory	The Johns Hopkins University Applied Physics Laboratory
	Email: Edward.Birrane@jhuapl.edu	Email: Edward.Birrane@jhuapl.edu


	Sarah E. Heiner	Sarah Heiner
	The Johns Hopkins University Applied Physics Laboratory	The Johns Hopkins University Applied Physics Laboratory
	Email: Sarah.Heiner@jhuapl.edu	Email: Sarah.Heiner@jhuapl.edu

	Emery Annis	Emery Annis
	The Johns Hopkins University Applied Physics Laboratory	The Johns Hopkins University Applied Physics Laboratory
	Email: Emery.Annis@jhuapl.edu	Email: Emery.Annis@jhuapl.edu

End of changes. 6 change blocks.
	11 lines changed or deleted	12 lines changed or added
This html diff was produced by rfcdiff 1.48.