rfc9290_extractedfrombefore.txt		rfc9290_extractedfromfinal.txt
	skipping to change at page 19, line 26 ¶		skipping to change at page 19, line 26 ¶
	656E # "en"		656E # "en"
	65 # text(5)		65 # text(5)
	48656C6C6F # "Hello"		48656C6C6F # "Hello"
	38(["fr", "Bonjour"])		38(["fr", "Bonjour"])
	D8 26 # tag(38)		D8 26 # tag(38)
	82 # array(2)		82 # array(2)
	62 # text(2)		62 # text(2)
	6672 # "fr"		6672 # "fr"
	67 # text(7)		67 # text(7)
	426F6E6A6F7572 # "Bonjour"		426F6E6A6F7572 # "Bonjour"
	􀔴􀔬􀔳􀕀		של􀔬􀔳 שלום
	38(["he", "􀔴􀔬􀔳􀕀", true])		38(["he", " של􀔬􀔳 שלום", true])
	D8 26 # tag(38)		D8 26 # tag(38)
	83 # array(3)		83 # array(3)
	62 # text(2)		62 # text(2)
	6865 # "he"		6865 # "he"
	68 # text(8)		68 # text(8)
	D7A9D79CD795D79D # "􀔴􀔬􀔳􀕀"		D7A9D79CD795D79D # " של􀔬􀔳 "שלום
	F5 # primitive(21)		F5 # primitive(21)
	Appendix B. Interworking with RFC 7807		Appendix B. Interworking with RFC 7807
	On certain occasions, it will be necessary to carry ("tunnel") problem details in a		On certain occasions, it will be necessary to carry ("tunnel") problem details in a
	Concise Problem Details data item.		Concise Problem Details data item.
	[RFC7807]		[RFC7807]
	RFC 9290 CoRE Problem Details September 2022		RFC 9290 CoRE Problem Details September 2022
	This appendix defines a Custom Problem Detail entry for that purpose. This is assigned Custom		This appendix defines a Custom Problem Detail entry for that purpose. This is assigned Custom
	Problem Detail key 7807 in Section 6.2. Its structure is:		Problem Detail key 7807 in Section 6.2. Its structure is:
	To carry an problem details JSON object in a Concise Problem Details data item, first		To carry an problem details JSON object in a Concise Problem Details data item, first
	convert the JSON object to CBOR as per Section 6.2 of RFC 8949 . Create an empty Concise		convert the JSON object to CBOR as per Section 6.2 of RFC 8949 . Create an empty Concise
End of changes. 2 change blocks.
	3 lines changed or deleted		3 lines changed or added
This html diff was produced by rfcdiff 1.48.