Month of April 2006 - Page Number 1

Showing 1 - 10 of 1,132 from April 2006
Browse Prior Art Database
  1. 1.
    IPCOM000135972D | Original Publication Date: 2006-Apr-30
  2. 2.
    This document specifies an extension to the multicast addressing architecture of the IPv6 protocol. The extension allows the use of Interface Identifiers (IIDs) to allocate multicast addresses. When a link-local unicast address is configured at each interface of a node, an IID is uniquely determined. After that,...
    IPCOM000135971D | Original Publication Date: 2006-Apr-01
  3. 3.
    This document defines several subcodes for the BGP Cease NOTIFICATION message that would provide more information to aid network operators in correlating network events and diagnosing BGP peering issues.
    IPCOM000135970D | Original Publication Date: 2006-Apr-01
  4. 4.
    This document describes how to construct DNSSEC NSEC resource records that cover a smaller range of names than called for by RFC 4034. By generating and signing these records on demand, authoritative name servers can effectively stop the disclosure of zone contents otherwise made possible by walking the chain of NSEC...
    IPCOM000135969D | Original Publication Date: 2006-Apr-01
  5. 5.
    This document is a compilation of issues found during six interoperability events and 5 years of experience with implementing, testing, and using Stream Control Transmission Protocol (SCTP) along with the suggested fixes. This document provides deltas to RFC 2960 and is organized in a time-based way. The issues are...
    IPCOM000135968D | Original Publication Date: 2006-Apr-01
  6. 6.
    The Border Gateway Protocol (BGP) is an inter-autonomous system routing protocol designed for TCP/IP internets. Typically, all BGP speakers within a single AS must be fully meshed so that any external routing information must be re-distributed to all other routers within that Autonomous System (AS). This represents...
    IPCOM000135967D | Original Publication Date: 2006-Apr-01
  7. 7.
    E-mail on the Internet can be forged in a number of ways. In particular, existing protocols place no restriction on what a sending host can use as the reverse-path of a message or the domain given on the SMTP HELO/EHLO commands. This document describes version 1 of the Sender Policy Framework (SPF) protocol, whereby...
    IPCOM000135966D | Original Publication Date: 2006-Apr-01
  8. 8.
    This document defines an algorithm by which, given an e-mail message, one can extract the identity of the party that appears to have most proximately caused that message to be delivered. This identity is called the Purported Responsible Address (PRA).
    IPCOM000135965D | Original Publication Date: 2006-Apr-01
  9. 9.
    Internet mail suffers from the fact that much unwanted mail is sent using spoofed addresses -- "spoofed" in this case means that the address is used without the permission of the domain owner. This document describes a family of tests by which SMTP servers can determine whether an e-mail address in a received message...
    IPCOM000135964D | Original Publication Date: 2006-Apr-01
  10. 10.
    This memo defines an extension to the Simple Mail Transfer Protocol (SMTP) service that allows an SMTP client to specify the responsible submitter of an e-mail message. The responsible submitter is the e-mail address of the entity most recently responsible for introducing a message into the transport stream. This...
    IPCOM000135963D | Original Publication Date: 2006-Apr-01