Context: The same character converted to UTF-8 becomes the byte sequence EF BB BF. The Unicode Standard allows that the BOM "can serve as signature for UTF-8 encoded text where the character set is unmarked". Some software developers have adopted it for other encodings, including UTF-8, in an attempt to distinguish UTF-8 from local 8-bit code pages. However RFC 3629, the UTF-8 standard, recommends that byte order marks be forbidden in protocols using UTF-8, but discusses the cases where this may not be possible. In addition, the large restriction on possible patterns in UTF-8 (for instance there cannot be any lone bytes with the high bit set) means that it should be possible to distinguish UTF-8 from other character encodings without relying on the BOM.

Question: What is the UTF-8 standard? 
Answer: RFC 3629

Question: Byte order marks are forbidden in protocols using what standard? 
Answer: UTF-8

Question: Why is it possible to distinguish UTF-8 from other protocols?
Answer: the large restriction on possible patterns

Question: BOM can not replace what kind of UTF-8 text?
Answer: Unanswerable

Question: What is used to distinguish local 8-bit code pages?
Answer: Unanswerable

Question: What is the name of the BOM standard?
Answer: Unanswerable

Question: What type of bytes are required in a high bit set?
Answer: Unanswerable

Question: What type of patterns are rarely resticted?
Answer: Unanswerable