IT. Expert System.


RFC (best current practice status)

An Appeal to the Internet Community to Return Unused IP Networks (Prefixes) to the IANA. P. Nesser II. February 1996. RFC1917. (Format: TXT=23623 bytes) (Also BCP0004) (Status: BEST CURRENT PRACTICE) (DOI: 10.17487 / RFC1917) [article]Address Allocation for Private Internets. Y. Rekhter, B. Moskowitz, D. Karrenberg, G. J. de Groot, E. Lear. February 1996. RFC1918. (Format: TXT=22270 bytes) (Obsoletes RFC1627, RFC1597) (Updated by RFC6761) (Also BCP0005) (Status: BEST CURRENT PRACTICE) (DOI: 10.17487 / RFC1918) [article]Administratively Scoped IP Multicast. D. Meyer. July 1998. RFC2365. (Format: TXT=17770 bytes) (Also BCP0023) (Status: BEST CURRENT PRACTICE) (DOI: 10.17487 / RFC2365) [article]Advancement of MIB specifications on the IETF Standards Track. M. O'Dell, H. Alvestrand, B. Wijnen, S. Bradner. October 1998. RFC2438. (Format: TXT=13633 bytes) (Also BCP0027) (Status: BEST CURRENT PRACTICE) (DOI: 10.17487 / RFC2438) [article]Anti-Spam Recommendations for SMTP MTAs. G. Lindberg. February 1999. RFC2505. (Format: TXT=53597 bytes) (Also BCP0030) (Status: BEST CURRENT PRACTICE) (DOI: 10.17487 / RFC2505) [article]A Transient Prefix for Identifying Profiles under Development by the Working Groups of the Internet Engineering Task Force. M. Rose. July 2002. RFC3349. (Format: TXT=7916 bytes) (Also BCP0059) (Status: BEST CURRENT PRACTICE) (DOI: 10.17487 / RFC3349) [article]Advice to link designers on link Automatic Repeat reQuest (ARQ). G. Fairhurst, L. Wood. August 2002. RFC3366. (Format: TXT=66097 bytes) (Also BCP0062) (Status: BEST CURRENT PRACTICE) (DOI: 10.17487 / RFC3366) [article]An IETF URN Sub-namespace for Registered Protocol Parameters. M. Mealling, L. Masinter, T. Hardie, G. Klyne. June 2003. RFC3553. (Format: TXT=14815 bytes) (Also BCP0073) (Status: BEST CURRENT PRACTICE) (DOI: 10.17487 / RFC3553) [article]A Practice for Revoking Posting Rights to IETF Mailing Lists. M. Rose. March 2004. RFC3683. (Format: TXT=15698 bytes) (Also BCP0083) (Status: BEST CURRENT PRACTICE) (DOI: 10.17487 / RFC3683) [article]Assigning Experimental and Testing Numbers Considered Useful. T. Narten. January 2004. RFC3692. (Format: TXT=15054 bytes) (Updates RFC2434) (Also BCP0082) (Status: BEST CURRENT PRACTICE) (DOI: 10.17487 / RFC3692) [article]Advice for Internet Subnetwork Designers. P. Karn, Ed., C. Bormann, G. Fairhurst, D. Grossman, R. Ludwig, J. Mahdavi, G. Montenegro, J. Touch, L. Wood. July 2004. RFC3819. (Format: TXT=152174 bytes) (Also BCP0089) (Status: BEST CURRENT PRACTICE) (DOI: 10.17487 / RFC3819) [article]A Model for IETF Process Experiments. J. Klensin, S. Dawkins. November 2004. RFC3933. (Format: TXT=14409 bytes) (Also BCP0093) (Status: BEST CURRENT PRACTICE) (DOI: 10.17487 / RFC3933) [article]A Mission Statement for the IETF. H. Alvestrand. October 2004. RFC3935. (Format: TXT=16639 bytes) (Also BCP0095) (Status: BEST CURRENT PRACTICE) (DOI: 10.17487 / RFC3935) [article]Avoiding Equal Cost Multipath Treatment in MPLS Networks. G. Swallow, S. Bryant, L. Andersson. June 2007. RFC4928. (Format: TXT=18376 bytes) (Updated by RFC7274) (Also BCP0128) (Status: BEST CURRENT PRACTICE) (DOI: 10.17487 / RFC4928) [article]ASCII Escaping of Unicode Characters. J. Klensin. February 2008. RFC5137. (Format: TXT=27742 bytes) (Also BCP0137) (Status: BEST CURRENT PRACTICE) (DOI: 10.17487 / RFC5137) [article]A Registry for SMTP Enhanced Mail System Status Codes. T. Hansen, J. Klensin. June 2008. RFC5248. (Format: TXT=23845 bytes) (Updates RFC3463, RFC4468, RFC4954) (Also BCP0138) (Status: BEST CURRENT PRACTICE) (DOI: 10.17487 / RFC5248) [article]An Architecture for Location and Location Privacy in Internet Applications. R. Barnes, M. Lepinski, A. Cooper, J. Morris, H. Tschofenig, H. Schulzrinne. July 2011. RFC6280. (Format: TXT=99801 bytes) (Updates RFC3693, RFC3694) (Also BCP0160) (Status: BEST CURRENT PRACTICE) (DOI: 10.17487 / RFC6280) [article]Algorithm Agility Procedure for the Resource Public Key Infrastructure (RPKI). R. Gagliano, S. Kent, S. Turner. April 2013. RFC6916. (Format: TXT=48395 bytes) (Also BCP0182) (Status: BEST CURRENT PRACTICE) (DOI: 10.17487 / RFC6916) [article]A Uniform Resource Name (URN) Namespace for Examples. P. Saint-Andre. May 2013. RFC6963. (Format: TXT=11749 bytes) (Also BCP0183) (Status: BEST CURRENT PRACTICE) (DOI: 10.17487 / RFC6963) [article]Autonomous System (AS) Reservation for Private Use. J. Mitchell. July 2013. RFC6996. (Format: TXT=8198 bytes) (Updates RFC1930) (Also BCP0006) (Status: BEST CURRENT PRACTICE) (DOI: 10.17487 / RFC6996) [article]An Acceptable Use Policy for New ICMP Types and Codes. M. Shore, C. Pignataro. May 2014. RFC7279. (Format: TXT=17829 bytes) (Also BCP0189) (Status: BEST CURRENT PRACTICE) (DOI: 10.17487 / RFC7279) [article]
Count of articles: 21

Android Reference

Java basics

Java Enterprise Edition (EE)

Java Standard Edition (SE)





Java Script








Design patterns

RFC (standard status)

RFC (proposed standard status)

RFC (draft standard status)

RFC (informational status)

RFC (experimental status)

RFC (best current practice status)

RFC (historic status)

RFC (unknown status)

IT dictionary

All information of this service is derived from the free sources and is provided solely in the form of quotations. This service provides information and interfaces solely for the familiarization (not ownership) and under the "as is" condition.
Copyright 2016 © ELTASK.COM. All rights reserved.
Site is optimized for mobile devices.
Downloads: 477 / 159531127. Delta: 0.00346 с