|
Internet Drafts - IDs for Oct/2008
Index - Month Index of IDs
All IDs - sorted by date)
30/10/2008
| |
|
| |
| | Congestion Control in the RFC Series |
| |
|
This document is an informational snapshot produced by the IRTF's Internet Congestion Control Research Group (ICCRG). It provides a survey of congestion control topics described by documents in the RFC series. This does not modify or update the specifications or status of the RFC documents that are discussed. It may be used as a reference or starting point for the future work of the research group, especially in noting gaps or open issues in the current IETF standards. |
27/10/2008
| |
|
| |
| | Y.1541-QOSM -- Y.1541 QoS Model for Networks Using Y.1541 QoS Classes |
| |
| | draft-ietf-nsis-y1541-qosm-07.txt |
| | Date: |
27/10/2008 |
| | Authors: |
Gerald Ash, Al Morton, Martin Dolly, Percy Tarapore, Chuck Dvorak, Yacine Mghazli |
| | Working Group: |
Next Steps in Signaling (nsis) |
| | Formats: |
txt xml |
|
This draft describes a QoS-NSLP QoS model (QOSM) based on ITU-T Recommendation Y.1541 Network QoS Classes and related signaling requirements. Y.1541 specifies 8 classes of Network Performance objectives, and the Y.1541-QOSM extensions include additional QSPEC parameters and QOSM processing guidelines. |
12/10/2008
| |
|
| |
| | Specifying Holes in LoST Service Boundaries |
| |
|
This document describes how holes can be specified in geodetic service boundaries. One means of implementing a search solution in a service database, such as one might provide with a LoST server, is described. |
09/10/2008
| |
|
| |
| | Combined Presence Schemas Utilizing RELAX NG |
| |
|
This memo describes a batch of Presence Information Data Format (PIDF) and its extension schemas written with the RELAX NG schema language. Unlike with the current W3C XML Schema language it is possible to write reasonable forwards and backwards compatible presence combination schemas. These RELAX NG schemas are stricter than the W3C Schemas and thus the instance documents that validate with these schemas follow the intended content model more closely. Especially, these schemas are targeted to actual implementations in order to decrease interoperability problems. |
07/10/2008
| |
|
| |
| | ForCES Forwarding Element Model |
| |
|
This document defines the forwarding element (FE) model used in the Forwarding and Control Element Separation (ForCES) protocol [2]. The model represents the capabilities, state and configuration of forwarding elements within the context of the ForCES protocol, so that control elements (CEs) can control the FEs accordingly. More specifically, the model describes the logical functions that are present in an FE, what capabilities these functions support, and how these functions are or can be interconnected. This FE model is intended to satisfy the model requirements specified in the ForCES requirements document, RFC3654 [6]. |
05/10/2008
| |
|
| |
| | IAX: Inter-Asterisk eXchange Version 2 |
| |
| | draft-guy-iax-05.txt |
| | Date: |
05/10/2008 |
| | Authors: |
Mark Spencer, Brian Capouch, Ed Guy, Frank Miller, Kenneth Shumard |
| | Working Group: |
Individual Submissions (none) |
| | Formats: |
txt xml |
|
This document describes IAX, the Inter-Asterisk eXchange protocol, an application-layer control and media protocol for creating, modifying, and terminating multimedia sessions over Internet Protocol (IP) networks. IAX was developed by the open source community for the Asterisk PBX and is targeted primarily at Voice over Internet Protocol (VoIP) call control, but it can be used with streaming video or any other type of multimedia. IAX is an "all in one" protocol for handling multimedia in IP networks. It combines both control and media services in the same protocol. In addition, IAX uses a single UDP data stream on a static port greatly simplifying Network Address Translation (NAT) gateway traversal, eliminating the need for other protocols to work around NAT, and simplifying network and firewall management. IAX employs a compact encoding which decreases bandwidth usage and is well suited for Internet telephony service. In addition, its open nature permits new payload types additions needed to support additional services. |
| | IANA Considerations for IAX: Inter-Asterisk eXchange Version 2 |
| |
|
This document establishes the IANA registries for IAX, the Inter- Asterisk eXchange protocol, an application-layer control and media protocol for creating, modifying, and terminating multimedia sessions over Internet Protocol (IP) networks. IAX was developed by the open source community for the Asterisk PBX and is targeted primarily at Voice over Internet Protocol (VoIP) call control, but it can be used with streaming video or any other type of multimedia. |
01/10/2008
| |
|
| |
| | EDI-INT Features Header |
| |
|
With the maturity of the EDI-INT standard of AS1, AS2 and AS3, applications and additional features are being built upon the basic secure transport functionality. These features are not necessarily supported by all EDI-INT applications and could cause potential problems with implementations. |
|
