Request for Comments - Wikipedia, the free encyclopedia(Site not responding. Last check: 2007-11-05)
RFCs can be obtained on the Internet from the RFC Editor [1], the IETF [2], or many other sites, principally using the Web, but also through anonymous FTP, gopher, and other Internet document-retrieval systems.
RFC 2047 specifies a standard way of encoding non US-ASCII characters into a string that identifies both the character set to use and the actual characters.
RFC3021 31-Bit Prefixes on IPv4 Links December 2000 (b) the link local (or limited) broadcast {-1, -1} {0, 0} The {0, 0} form of a limited broadcast is obsolete, but may still be present in a network.
RFC3021 31-Bit Prefixes on IPv4 Links December 2000 to-point link with a 31-bit mask.
RFC3021 31-Bit Prefixes on IPv4 Links December 2000 In a point-to-point link with a 31-bit mask, the configuration of such a mask SHOULD allow for the generation of datagrams addressed to { , 0 }.
Standards Track [Page 3] RFC3021 31-Bit Prefixes on IPv4 Links December 2000 (b) the link local (or limited) broadcast {-1, -1} {0, 0} The {0, 0} form of a limited broadcast is obsolete, but may still be present in a network.
Furthermore, the communication between peers is done using multicast, limited broadcast or unicast addresses (all on the local network), none of which are affected with the use of 31-bit subnet masks.
Standards Track [Page 6] RFC3021 31-Bit Prefixes on IPv4 Links December 2000 In a point-to-point link with a 31-bit mask, the configuration of such a mask SHOULD allow for the generation of datagrams addressed to { , 0 }.
RFC3021 31-Bit Prefixes on IPv4 Links December 2000 - Deployment of a new Internet Protocol to increase the size of the address space.
The use of host addresses allows for the assignment of IP addresses belonging to different networks at each side of the link, causing link and network management not to be straight forward.
Existing documentation [RFC 950] has already hinted at the possible use of a 1-bit wide host-number field.
RFC3021 - Using 31-Bit Prefixes on IPv4 Point-to-Point Links
Among other people, we would like to acknowledge Alex Zinin for his comments, and the many people who have tested 31 bit subnet masks in their labs and networks.
Acknowledgement Funding for the RFC Editor function is currently provided by the Internet Society.
www.faqs.org /rfcs/rfc3021.html (2265 words)
Seekmeup.Directory - Computers: Internet: RFCs: 3001 - 3100(Site not responding. Last check: 2007-11-05)
RFC 3026 - Liaison to IETF/ISOC on ENUM.
RFC 3033 - The Assignment of the Information Field and Protocol Identifier in the Q.2941 Generic Identifier and Q.2957 User-to-user Signaling for the Internet Protocol.
RFC 3068 - An Anycast Prefix for 6to4 Relay Routers.
RFC 1991(Site not responding. Last check: 2007-11-05)
Informational [Page 3] RFC 1991 PGP Message Exchange Formats August 1996 -the receiving PGP decrypts the message using the session key Both digital signature and confidentiality services may be applied to the same message.
Informational [Page 10] RFC 1991 PGP Message Exchange Formats August 1996 Other characteristics of the packet are determined by the type of the packet.
Informational [Page 13] RFC 1991 PGP Message Exchange Formats August 1996 6.2.1 Message-digest-related fields The message digest algorithm is specified by the message digest (MD) number of field (g).
Request for Comments(Site not responding. Last check: 2007-11-05)
RFC are published by the RFC Editor who is under the general direction of the IAB.
RFCs can be obtained on the Internet from http://www.ietf.org/rfc.html or many other sites, using anonymous FTP, gopher, and other Internet document-retrieval systems.
RFC3021 31-Bit Prefixes on IPv4 Links December 2000 3.
If these packets are not silently discarded, they MUST be treated as IP broadcasts [RFC 1812].
However, in the case where the originator is one of the endpoints of a point-to-point link with a 31-bit mask, it can also be used as a source address.
3001 - 3100 : Computers : Internet : RFCs : 3001 - 3100(Site not responding. Last check: 2007-11-05)
RFC 3033: The Assignment of the Information Field and Protocol Identifier in the Q.2941 Generic Identifier and Q.2957 User-to-user Signaling for the Internet Protocol.
RFC 3068: An Anycast Prefix for 6to4 Relay Routers.
RFC 3086: Definition of Differentiated Services Per Domain Behaviors and Rules for their Specification.
One such change, proposed by this document, is to halve the amount of address space assigned to point-to-point links (common throughout the Internet infrastructure) by allowing the use of 31-bit subnet masks in a very limited way.
For example: To: rfc-info@RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG.
Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG.
One > such change, proposed by this document, is to halve the amount of > address space assigned to point-to-point links (common throughout the > Internet infrastructure) by allowing the use of 31-bit subnet masks > in a very limited way.
For example: > > To: rfc-info@localhost > Subject: getting rfcs > > help: ways_to_get_rfcs > > Requests for special distribution should be addressed to either the > author of the RFC in question, or to RFC-Manager@localhost.
Unless > specifically noted otherwise on the RFC itself, all RFCs are for > unlimited distribution.echo > Submissions for Requests for Comments should be sent to > RFC-EDITOR@localhost.
RFC3021(Site not responding. Last check: 2007-11-05)
Network Working Group A. Retana Request for Comments: 3021 R. White Category: Standards Track Cisco Systems V.
McPherson Amber Networks December 2000 Using 31-Bit Prefixes on IPv4 Point-to-Point Links Status of this Memo This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements.
RFC3021 31-Bit Prefixes on IPv4 Links December 2000
Using a 31-bit prefix length leaves only two numbering possibilities (see Section 2.1), eliminating the use of a directed broadcast to the link (see Section 2.2.1).
Recommendations The considerations presented in Section 2 affect other published work.
The following text is added to section 4.3.3.9: The 255.255.255.255 IP broadcast address MUST be used for broadcast Address Mask Replies in point-to-point links with 31-bit subnet masks 4.
RFC 3021 - web hosting by Directi(Site not responding. Last check: 2007-11-05)
Communication Layers", STD 3, RFC 1122, October 1989.
[RFC1700] Reynolds, J. and J. Postel, "Assigned Numbers", STD 2, RFC
[RFC1812] Baker, F., "Requirements for IP Version 4 Routers", RFC
rfc-3021.rfclist.org /rfc-3021-8.htm (149 words)
rfc 3021 reference for Windows Api programming in C# , VB.NET, and VB6. Examples of P/Invoke and DllImport with Source ...(Site not responding. Last check: 2007-11-05)
rfc3021 reference for Windows Api programming in C#, VB.NET, and VB6.
Standards Track [Page 6] RFC3021 31-Bit Prefixes on IPv4 Links December 2000 In a point-to-point link with a 31-bit mask, the configuration of such a mask SHOULD allow for the generation of datagrams addressed to {