rfc is request for comment . it is used for discussion and development of new protocol and technique for use on the internet.
Both RFC 349 and RFC 1700 have an Assignment number and both have wide standard functions. They also offer applications that offer link, socket, port, and protocol.
1.application: e-mail application-layer protocol: SMTP [RFC 2821] 2.application: WEB application-layer protocol: HTTP [RFC 2616] 3.application: streaming multimedia application-layer protocol: HTTP (eg Youtobe), RTP [RFC 1889] 4.application:file transfer application-layer protocol: FTP [RFC 959] 5.application: remote terminal access application-layer protocol: Tenet [RFC 854]
origine of rfc? and what is rfc 1000? by taghazzul
RFC stand for "Request for comment" it is method for standard the network thing
IGRP - Interior Gateway Routing Protocol EIGRP- Enhanced Interior Gateway Routing Protocol
The new RFC on EIGRP, specifically RFC 7868, was published to formally document Enhanced Interior Gateway Routing Protocol (EIGRP) as an open standard protocol. This RFC describes EIGRP's operation, features, and mechanisms for network routing, ensuring interoperability among different vendors. By standardizing EIGRP, the RFC allows for broader adoption and implementation across various networking environments. This marks a significant step in promoting EIGRP as a widely recognized and utilized routing protocol beyond proprietary implementations.
1519
rfc is request for comment . it is used for discussion and development of new protocol and technique for use on the internet.
Both RFC 349 and RFC 1700 have an Assignment number and both have wide standard functions. They also offer applications that offer link, socket, port, and protocol.
Internet Official Protocol Standards
Point-to-Point Protocol.
RFC 349 and RFC 1700 both pertain to the allocation and management of Internet protocol parameters. RFC 1700, titled "Assigned Numbers," provides a registry of well-known port numbers and protocol identifiers used in Internet communications. RFC 349, which updates RFC 1700, offers a more organized approach to the assignment of these parameters, emphasizing the need for a structured method to manage them effectively. Both documents aim to ensure consistency and clarity in the use of Internet protocol specifications.
IP Security Protocol (IPSec)
1.application: e-mail application-layer protocol: SMTP [RFC 2821] 2.application: WEB application-layer protocol: HTTP [RFC 2616] 3.application: streaming multimedia application-layer protocol: HTTP (eg Youtobe), RTP [RFC 1889] 4.application:file transfer application-layer protocol: FTP [RFC 959] 5.application: remote terminal access application-layer protocol: Tenet [RFC 854]
A Request For Comments (RFC) document defines a protocol or policy used on the Internet. An RFC can be submitted by anyone. Eventually, if it gains enough interest, it may evolve into an Internet Standard Each RFC is designated by an RFC number. Once published, an RFC never changes. Modifications to an original RFC are assigned a new RFC number.
There are several RFCs that discuss classless inter-domain-routing. I believe the most informative for a novice would be RFC 4632 which obsoletes RFC 1519. This RFC is aimed at the IPv4 32 bit addressing scheme. Discusses IPv4 address exhaustion. This was the primary reason for CIDR or VLSM (Variable Length Subnet Mask) Discusses original classful address ranges Class A, B and C This would be a good start