rfc9277v3.txt		rfc9277.txt
	skipping to change at line 113 ¶		skipping to change at line 113 ¶
	on a damaged system, being able to identify the type of information		on a damaged system, being able to identify the type of information
	stored in a file can become very important.		stored in a file can become very important.
	A common way to identify the type of a file from its contents is to		A common way to identify the type of a file from its contents is to
	place a "magic number" at the start of the file contents [MAGIC]. In		place a "magic number" at the start of the file contents [MAGIC]. In
	the media type registration template [RFC6838], a magic number is		the media type registration template [RFC6838], a magic number is
	asked for, if available, as is a file extension.		asked for, if available, as is a file extension.
	A challenge for the file(1) command is often that it can be confused		A challenge for the file(1) command is often that it can be confused
	by recognizing the overall encoding but not the content being		by recognizing the overall encoding but not the content being
	encoded. For instance, an Android APK (as used to transfer and store		encoded. For instance, an Android Package Kit APK (as used to
	an application) may be identified as a ZIP file. Additionally, both		transfer and store an application) may be identified as a ZIP file.
	OpenOffice and MSOffice files are ZIP files of XML files; the		Additionally, both OpenOffice and MSOffice files are ZIP files of XML
	identification may stop at identifying them as ZIP files.		files; the identification may stop at identifying them as ZIP files.
	As CBOR becomes a more and more common encoding for a wide variety of		As CBOR becomes a more and more common encoding for a wide variety of
	artifacts, identifying them as just "CBOR" is probably not		artifacts, identifying them as just "CBOR" is probably not
	sufficient. This document provides a way to encode a magic number		sufficient. This document provides a way to encode a magic number
	into the beginning of a CBOR format file. As a CBOR format may use a		into the beginning of a CBOR format file. As a CBOR format may use a
	single CBOR data item or a CBOR sequence of data items [RFC8742], two		single CBOR data item or a CBOR sequence of data items [RFC8742], two
	possible methods of enveloping data are presented; a CBOR Protocol		possible methods of enveloping data are presented; a CBOR Protocol
	designer will specify one. (A CBOR Protocol is a specification that		designer will specify one. (A CBOR Protocol is a specification that
	uses CBOR as its encoding.)		uses CBOR as its encoding.)
End of changes. 1 change blocks.
	4 lines changed or deleted		4 lines changed or added
This html diff was produced by rfcdiff 1.48.