5. What Do Rfc 349 And Rfc 1700 Have In Common?
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
What do RFC 349 and RFC 1700 have in common?
Answer: The RFC 349 and RFC 1700 both have the assignment number and they have a wide function to perform. They provide the application which gives the link, socket .port, and different protocols.
What do you know about RFC?
RFC stands for “request for comments” it is a document which describe by the internet engineering task force (IETF) and it is due to the drafting and the views of the interested parties. It gives a lot of information. For those who want to become the internet standards, the end version of an RFC becomes the standard and no further changes are needed to execute. The document describes the standard since 1969.
About 2400 requests for comments (RFCs) are printed on different protocols, process applications, and concepts. A protocol like TCP/IP is formed by agreement rather than the committee. The ISOC member submits the FRC for acceptance and the submission of the documents done with the IETF. The RFC after the publication has the classification described in the following sections:
As the RFC is published it went through many tests and discussions by groups and individuals.it can go through different stages of development:
RFC Sub-series
The series of the RFC has three-subseries RFCs: BCP FYI and STD. the best practice BCP is the mandatory sub-series of IETF and not of the standard tracks. While the FYI is a sub-series of informational RFC which is encouraged by the specific RFC 1150. the STD is the third sub-series of the specific RFC 2026.
Streams of RFC
There are four RFC streams: IETF, IRTF, IAB, and Independent Submission. Only the IETF creates BCPs and RFCs on the standards track. The IESG oversees an independent dispatch for conflicts with the work of the IETF; quality is assessed by an independent editorial board. In other words, independent IRTFs and RFCs are supposed to contain information or experiences relating to the Internet in general that do not conflict with the work of the IETF; compare RFC 4846, RFC 5742, and RFC 5744.
Some of the RFCs with their title are described in the following:
Both RFC 349 and RFC 1700 are part of the Internet Protocol (IP) address space management process. The main purpose of both RFCs is to determine the distribution of IP addresses within a given region and assign them appropriately for its use. Both documents are also concerned with the registration of networks, but RFC 349 focuses specifically on the registration of European networks while RFC 1700 covers general updates and official assignments of the IP address space.