IT. Expert System.

RESULT:

RFC (best current practice status)

Guidelines for creation, selection, and registration of an Autonomous System (AS). J. Hawkinson, T. Bates. March 1996. RFC1930. (Format: TXT=22073 bytes) (Updated by RFC6996, RFC7300) (Also BCP0006) (Status: BEST CURRENT PRACTICE) (DOI: 10.17487 / RFC1930) [article]Guide for Internet Standards Writers. G. Scott. June 1998. RFC2360. (Format: TXT=47280 bytes) (Also BCP0022) (Status: BEST CURRENT PRACTICE) (DOI: 10.17487 / RFC2360) [article]Guidelines for Writing an IANA Considerations Section in RFCs. T. Narten, H. Alvestrand. October 1998. RFC2434. (Format: TXT=25092 bytes) (Obsoleted by RFC5226) (Updated by RFC3692) (Status: BEST CURRENT PRACTICE) (DOI: 10.17487 / RFC2434) [article]Guidelines for Writers of RTP Payload Format Specifications. M. Handley, C. Perkins. December 1999. RFC2736. (Format: TXT=24143 bytes) (Also BCP0036) (Status: BEST CURRENT PRACTICE) (DOI: 10.17487 / RFC2736) [article]GLOP Addressing in 233/8. D. Meyer, P. Lothberg. September 2001. RFC3180. (Format: TXT=8225 bytes) (Obsoletes RFC2770) (Also BCP0053) (Status: BEST CURRENT PRACTICE) (DOI: 10.17487 / RFC3180) [article]Guidelines for Evidence Collection and Archiving. D. Brezinski, T. Killalea. February 2002. RFC3227. (Format: TXT=18468 bytes) (Also BCP0055) (Status: BEST CURRENT PRACTICE) (DOI: 10.17487 / RFC3227) [article]Guidelines for the Use of Extensible Markup Language (XML) within IETF Protocols. S. Hollenbeck, M. Rose, L. Masinter. January 2003. RFC3470. (Format: TXT=64252 bytes) (Also BCP0070) (Status: BEST CURRENT PRACTICE) (DOI: 10.17487 / RFC3470) [article]Guidelines for Writing RFC Text on Security Considerations. E. Rescorla, B. Korver. July 2003. RFC3552. (Format: TXT=110393 bytes) (Also BCP0072) (Status: BEST CURRENT PRACTICE) (DOI: 10.17487 / RFC3552) [article]Guidelines for Cryptographic Key Management. S. Bellovin, R. Housley. June 2005. RFC4107. (Format: TXT=14752 bytes) (Also BCP0107) (Status: BEST CURRENT PRACTICE) (DOI: 10.17487 / RFC4107) [article]Guidelines for Authors and Reviewers of MIB Documents. C. Heard, Ed.. September 2005. RFC4181. (Format: TXT=102521 bytes) (Updated by RFC4841) (Also BCP0111) (Status: BEST CURRENT PRACTICE) (DOI: 10.17487 / RFC4181) [article]Guidelines and Registration Procedures for New URI Schemes. T. Hansen, T. Hardie, L. Masinter. February 2006. RFC4395. (Format: TXT=31933 bytes) (Obsoletes RFC2717, RFC2718) (Obsoleted by RFC7595) (Status: BEST CURRENT PRACTICE) (DOI: 10.17487 / RFC4395) [article]Guidance for Authentication, Authorization, and Accounting (AAA) Key Management. R. Housley, B. Aboba. July 2007. RFC4962. (Format: TXT=54927 bytes) (Also BCP0132) (Status: BEST CURRENT PRACTICE) (DOI: 10.17487 / RFC4962) [article]Guidelines for Writing an IANA Considerations Section in RFCs. T. Narten, H. Alvestrand. May 2008. RFC5226. (Format: TXT=66160 bytes) (Obsoletes RFC2434) (Also BCP0026) (Status: BEST CURRENT PRACTICE) (DOI: 10.17487 / RFC5226) [article]Guidelines for Specifying the Use of IPsec Version 2. S. Bellovin. February 2009. RFC5406. (Format: TXT=30393 bytes) (Also BCP0146) (Status: BEST CURRENT PRACTICE) (DOI: 10.17487 / RFC5406) [article]Guidance on Interoperation and Implementation Reports for Advancement to Draft Standard. L. Dusseault, R. Sparks. September 2009. RFC5657. (Format: TXT=29327 bytes) (Updates RFC2026) (Also BCP0009) (Status: BEST CURRENT PRACTICE) (DOI: 10.17487 / RFC5657) [article]Guidelines for the Use of the "OAM" Acronym in the IETF. L. Andersson, H. van Helvoort, R. Bonica, D. Romascanu, S. Mansfield. June 2011. RFC6291. (Format: TXT=16696 bytes) (Also BCP0161) (Status: BEST CURRENT PRACTICE) (DOI: 10.17487 / RFC6291) [article]Guidelines for Considering New Performance Metric Development. A. Clark, B. Claise. October 2011. RFC6390. (Format: TXT=49930 bytes) (Also BCP0170) (Status: BEST CURRENT PRACTICE) (DOI: 10.17487 / RFC6390) [article]Guidelines for Authors and Reviewers of IP Flow Information Export (IPFIX) Information Elements. B. Trammell, B. Claise. September 2013. RFC7013. (Format: TXT=76406 bytes) (Also BCP0184) (Status: BEST CURRENT PRACTICE) (DOI: 10.17487 / RFC7013) [article]Guidelines for Creating New DHCPv6 Options. D. Hankins, T. Mrugalski, M. Siodelski, S. Jiang, S. Krishnan. May 2014. RFC7227. (Format: TXT=83694 bytes) (Updates RFC3315) (Also BCP0187) (Status: BEST CURRENT PRACTICE) (DOI: 10.17487 / RFC7227) [article]Guidelines and Registration Procedures for URI Schemes. D. Thaler, Ed., T. Hansen, T. Hardie. June 2015. RFC7595. (Format: TXT=42897 bytes) (Obsoletes RFC4395) (Also BCP0035) (Status: BEST CURRENT PRACTICE) (DOI: 10.17487 / RFC7595) [article]Guidelines for Cryptographic Algorithm Agility and Selecting Mandatory-to-Implement Algorithms. R. Housley. November 2015. RFC7696. (Format: TXT=50543 bytes) (Also BCP0201) (Status: BEST CURRENT PRACTICE) (DOI: 10.17487 / RFC7696) [article]
Count of articles: 21
Content

Android Reference

Java basics

Java Enterprise Edition (EE)

Java Standard Edition (SE)

SQL

HTML

PHP

CSS

Java Script

MYSQL

JQUERY

VBS

REGEX

C

C++

C#

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

License.
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: 1439 / 96048279. Delta: 0.11201 с