|
Internet Drafts - IDs for Dec/2007
Index - Month Index of IDs
All IDs - sorted by date)
24/12/2007
| |
|
| |
| | SIEVE Email Filtering: Extension for Notifications |
| |
| | draft-ietf-sieve-notify-12.txt |
| | Date: |
24/12/2007 |
| | Authors: |
Alexey Melnikov, Barry Leiba, Wolfgang Segmuller, Tim Martin |
| | Working Group: |
Sieve Mail Filtering Language (sieve) |
| | Formats: |
txt |
|
Users go to great lengths to be notified as quickly as possible that they have received new mail. Most of these methods involve polling to check for new messages periodically. A push method handled by the final delivery agent gives users quicker notifications and saves server resources. This document does not specify the notification method but it is expected that using existing instant messaging infrastructure such as XMPP, or GSM Short Message Service (SMS) messages will be popular. This draft describes an extension to the Sieve mail filtering language that allows users to give specific rules for how and when notifications should be sent. |
22/12/2007
| |
|
| |
| | Hash Based Addresses (HBA) |
| |
|
This memo describes a mechanism to provide a secure binding between the multiple addresses with different prefixes available to a host within a multihomed site. This mechanism employs either Cryptographically Generated Addresses (CGAs) or a new variant of the same theme that uses the same format in the addresses. The main idea in the new variant is that information about the multiple prefixes is included within the addresses themselves. This is achieved by generating the interface identifiers of the addresses of a host as hashes of the available prefixes and a random number. Then, the multiple addresses are generated by prepending the different prefixes to the generated interface identifiers. The result is a set of addresses, called Hash Based Addresses (HBAs), that are inherently bound to each other. |
21/12/2007
| |
|
| |
| | The Lightweight Global Navigation Satellite System (GNSS) Support Protocol (LGSP) |
| |
| | draft-tyson-lgsp-01.txt |
| | Date: |
21/12/2007 |
| | Authors: |
Mike Tyson, Carlo Kopp |
| | Working Group: |
Individual Submissions (none) |
| | Formats: |
txt |
|
This document presents the Lightweight GNSS (Global Navigation Satellite System) Support Protocol (LGSP). The Lightweight GNSS Support Protocol (LGSP) is being developed in order to provide a comprehensive solution which solves the problems inherent in traditional radio-based Differential GPS (DGPS) protocols. LGSP will also provide additional support for GNSS user equipment, such as a GPS almanac retrieval method, allowing compatible units to perform faster almanac acquisition, thus resulting in less time until an initial position measurement can be established. Other supporting features include alternative distribution of GPS navigation messages and differential correction messages, a hierarchical mirroring architecture, redundant backup operation and load balancing functions. |
| | Multiple-Recipient MESSAGE Requests in the Session Initiation Protocol (SIP) |
| |
|
This document specifies a mechanism that allows a SIP User Agent Client (UAC) to send a SIP MESSAGE request to a set of destinations, by using a SIP URI-list (Uniform Resource Identifier list) service. The UAC sends a SIP MESSAGE request that includes the payload along with the URI list to the MESSAGE URI-list service, which sends a MESSAGE request including the payload to each of the URIs included in the list. |
18/12/2007
| |
|
| |
| | PPP Over Ethernet (PPPoE) Extensions for Scaled Credits and Link Metrics |
| |
|
This document specifies a method for optional flow control credit scaling and link quality metric scaling for Point-to-Point over Ethernet (PPPoE). Credit and metric scaling is required when connecting to high performance devices that employ the PPPoE credit flow control and link metric reports as defined in RFC 4938. |
| | Packet Sampling (PSAMP) Protocol Specifications |
| |
|
This document specifies the export of packet information from a PSAMP Exporting Process to a PSAMP Collecting Process. For export of packet information the IP Flow Information eXport (IPFIX) protocol is used, as both the IPFIX and PSAMP architecture match very well and the means provided by the IPFIX protocol are sufficient. The document specifies in detail how the IPFIX protocol is used for PSAMP export of packet information. |
| | Referring to Multiple Resources in the Session Initiation Protocol (SIP) |
| |
| | draft-ietf-sip-multiple-refer-03.txt |
| | Date: |
18/12/2007 |
| | Authors: |
Gonzalo Camarillo, Aki Niemi, Markus Isomaki, Miguel Garcia-Martin, Hisham Khartabil |
| | Working Group: |
Session Initiation Protocol (sip) |
| | Formats: |
xml txt |
|
This document defines extensions to the SIP REFER method so that this method can be used to refer to multiple resources in a single request. These extensions include the use of pointers to Uniform Resource Identifier (URI)-lists in the Refer-To header field and the "multiple-refer" SIP option-tag. |
14/12/2007
| |
|
| |
| | Session Initiation Protocol Call Control - Transfer |
| |
|
This document describes providing Call Transfer capabilities in the Session Initiation Protocol (SIP). SIP extensions such as REFER and Replaces are used to provide a number of transfer services including blind transfer, consultative transfer, and attended transfer. This work is part of the SIP multiparty call control framework. |
04/12/2007
| |
|
| |
| | Multicast Group Membership Discovery MIB |
| |
|
This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes objects used for managing the Internet Group Management Protocol (IGMP) and the Multicast Listener Discovery (MLD) protocol. |
03/12/2007
| |
|
| |
| | Preventing Use of Recursive Nameservers in Reflector Attacks |
| |
|
This document describes ways to prevent the use of default configured recursive nameservers as reflectors in Denial of Service (DoS) attacks. Recommended configuration as measures to mitigate the attack are given. |
| | The E.164 to Uniform Resource Identifiers (URI) Dynamic Delegation Discovery System (DDDS) Application for Infrastructure ENUM |
| |
|
This document defines the use case for Infrastructure ENUM and proposes its implementation as a parallel namespace to "e164.arpa" as defined in RFC3761, as the long-term solution to the problem of allowing carriers to provision DNS records for telephone numbers independently of those provisioned by end users (number assignees). |
|
