language:
Find link is a tool written by Edward Betts.searching for Best current practice 17 found (29 total)
alternate case: best current practice
IPsec
(5,081 words)
[view diff]
no match in snippet
view article
find links to article
In computing, Internet Protocol Security (IPsec) is a secure network protocol suite that authenticates and encrypts packets of data to provide secure encryptedUniform Resource Name (1,557 words) [view diff] case mismatch in snippet view article find links to article
Mechanisms. Network Working Group. doi:10.17487/RFC3406. RFC 3406. Best Current Practice. Obsoleted by RFC 8141. Obsoletes RFC 2611. T. Berners-Lee; R. Fielding;IETF language tag (3,230 words) [view diff] case mismatch in snippet view article find links to article
been standardized by the Internet Engineering Task Force (IETF) in Best Current Practice (BCP) 47; the subtags are maintained by the IANA Language SubtagLanguage code (272 words) [view diff] case mismatch in snippet view article find links to article
Locale (computer software) "Information on BCP 47 » RFC Editor". Best Current Practice 47 – Tags for Identifying Languages, IETF "The Linguasphere Register.test (283 words) [view diff] case mismatch in snippet view article find links to article
S2CID 260466. As a way to avoid this problem, the IETF published Best Current Practice (BCP) 32 in 1999. BCP 32, also known as RFC 2606, defines four reservedMichael Mealling (877 words) [view diff] case mismatch in snippet view article find links to article
3688 (BCP0081) "The IETF XML Registry" M. Mealling. January 2004.BEST CURRENT PRACTICE RFC 3622 "A Uniform Resource Name (URN) Namespace for the LibertyPaul Vixie (960 words) [view diff] case mismatch in snippet view article find links to article
the author of several Request for Comments (RFC)s, including a Best Current Practice document on "Classless IN-ADDR.ARPA Delegation" (BCP 20), and someReserved IP addresses (648 words) [view diff] case mismatch in snippet view article find links to article
Engineering Task Force. doi:10.17487/RFC7526. BCP 196. RFC 7526. Best Current Practice. Obsoletes RFC 3068 and 6732. C. Huitema (June 2001). An AnycastISO 639-3 (2,785 words) [view diff] case mismatch in snippet view article find links to article
Internet Engineering Task Force (IETF), as documented in: BCP 47: Best Current Practice 47, which includes RFC 5646 RFC 5646, which superseded RFC 4646IPv4 (5,544 words) [view diff] case mismatch in snippet view article find links to article
Engineering Task Force. doi:10.17487/RFC7526. BCP 196. RFC 7526. Best Current Practice. Obsoletes RFC 3068 and 6732. C. Huitema (June 2001). An AnycastAnycast (2,157 words) [view diff] case mismatch in snippet view article find links to article
Engineering Task Force. doi:10.17487/RFC7526. BCP 196. RFC 7526. Best Current Practice. Obsoletes RFC 3068 and 6732. "Anycast Rendezvous Point". CiscoInteroperable Master Format (1,033 words) [view diff] exact match in snippet view article find links to article
technologists, logistics specialists and software providers on best current practice for delivering large volumes of localized content in a resourceMulticast address (1,813 words) [view diff] case mismatch in snippet view article find links to article
specified in RFC 5771, an Internet Engineering Task Force (IETF) Best Current Practice document (BCP 51). The address range is divided into blocks eachInternet Standard (3,905 words) [view diff] case mismatch in snippet view article find links to article
Standard. The Internet Standards Process is defined in several "Best Current Practice" documents, notably BCP 9 (currently[update] RFC 2026 and RFC 6410)Brian Carpenter (engineer) (894 words) [view diff] case mismatch in snippet view article
Engineering Task Force. doi:10.17487/RFC7526. BCP 196. RFC 7526. Best Current Practice. Obsoletes RFC 3068 and 6732. K. Nichols; B. Carpenter (April 2001)IPv6 address (8,329 words) [view diff] case mismatch in snippet view article find links to article
Engineering Task Force. doi:10.17487/RFC7526. BCP 196. RFC 7526. Best Current Practice. Obsoletes RFC 3068 and 6732. R. Hinden; B. Haberman (October 2005)PL/I (11,890 words) [view diff] exact match in snippet view article find links to article
controlling date representations and additions to bring time and date to best current practice. New functions for manipulating dates include – DAYS and DAYSTODATE