Tools
Sorted by:
Try your query at:
 |
 |
 |
 |
 |
 |
Results 1 - 10
of
743,372
Internet Engineering Task Force
, 2001
"... Status of this Memo Internet Official Protocol Standards This memo is an Internet Standard. Distribution of this memo is unlimited. Copyright Notice Copyright (C) The Internet Society (2001). All Rights Reserved. This memo contains a snapshot of the state of standardization of protocols used in the ..."
Abstract
-
Cited by 2 (0 self)
- Add to MetaCart
Status of this Memo Internet Official Protocol Standards This memo is an Internet Standard. Distribution of this memo is unlimited. Copyright Notice Copyright (C) The Internet Society (2001). All Rights Reserved. This memo contains a snapshot of the state of standardization of protocols used
Internet Engineering Task Force
, 2013
"... Multiplexing Negotiation Using ICE Candidate Extension draft-hutton-mmusic-bundled-ice-candidates-00 This document describes a mechanism for extending ICE candidates with an optional parameter which can be used to negotiate the usage of bundled media, which refers to the usage of a single 5-tuple fo ..."
Abstract
- Add to MetaCart
Multiplexing Negotiation Using ICE Candidate Extension draft-hutton-mmusic-bundled-ice-candidates-00 This document describes a mechanism for extending ICE candidates with an optional parameter which can be used to negotiate the usage of bundled media, which refers to the usage of a single 5-tuple for multiple RTP streams. In a scenario where a party initiating the negotiation supports ICE [RFC5245] this mechanism provides the ability to provide an SDP offer which is both backwards compatible and able to fully specify the use of bundled media. Therefore, this mechanism allows bundled and non-bundled media to be negotiated in a single offer/answer exchange when both parties support ICE and this extension. The mechanism complements the procedures described in [draft-ietf-mmusic-sdp-bundle-negotiation].
Internet Engineering Task Force
, 2011
"... IW10 Considered Harmful draft-gettys-iw10-considered-harmful-00 The proposed change to the initial window to 10 indraft-ietf-tcpminitcwnd must be considered deeply harmful; not because it is the proposed change is evil taken in isolation, but that other changes in web browsers and web sites that hav ..."
Internet Engineering Task Force (IETF)
"... This document is the revised protocol definition for Internationalized Domain Names (IDNs). The rationale for changes, the relationship to the older specification, and important terminology are provided in other documents. This document specifies the protocol mechanism, called Internationalized Doma ..."
Abstract
- Add to MetaCart
Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the
Internet Engineering Task Force (IETF)
, 2011
"... Rationale for Update to the IPv6 Flow Label Specification Various published proposals for use of the IPv6 flow label are incompatible with its original specification in RFC 3697. Furthermore, very little practical use is made of the flow label, partly due to some uncertainties about the correct inte ..."
Abstract
- Add to MetaCart
. This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Not all documents approved by the IESG are a candidate for any level
Internet Engineering Task Force (IETF)
, 2011
"... Location-to-Service Translation (LoST) maps service identifiers and location information to service contact URIs. If a LoST client wants to discover available services for a particular location, it will perform a <listServicesByLocation> query to the LoST server. However, the LoST server, in i ..."
Abstract
- Add to MetaCart
an Experimental Protocol for the Internet community. This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Not all documents
Internet Engineering Task Force (IETF)
, 2011
"... Requirements for Management of Name Servers for the DNS Management of name servers for the Domain Name System (DNS) has traditionally been done using vendor-specific monitoring, configuration, and control methods. Although some service monitoring platforms can test the functionality of the DNS itsel ..."
Abstract
- Add to MetaCart
This document is not an Internet Standards Track specification; it is published for informational purposes. This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication
Internet Engineering Task Force (IETF)
"... Tunnelling of Explicit Congestion Notification This document redefines how the explicit congestion notification (ECN) field of the IP header should be constructed on entry to and exit from any IP-in-IP tunnel. On encapsulation, it updates RFC 3168 to bring all IP-in-IP tunnels (v4 or v6) into line w ..."
Abstract
- Add to MetaCart
that to include tunnelling issues. Status of This Memo This is an Internet Standards Track document. This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the
Internet Engineering Task Force (IETF)
, 2012
"... Asymmetric Extended Route Optimization (AERO) Nodes attached to common multi-access link types (e.g., multicastcapable, shared media, non-broadcast multiple access (NBMA), etc.) can exchange packets as neighbors on the link, but they may not always be provisioned with sufficient routing information ..."
Abstract
- Add to MetaCart
for examination, experimental implementation, and evaluation. This document defines an Experimental Protocol for the Internet community. This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved
Internet Engineering Task Force (IETF)
"... Implementation Status The DNS Security Extensions (DNSSEC) requires the use of cryptographic algorithm suites for generating digital signatures over DNS data. There is currently an IANA registry for these algorithms, but there is no record of the recommended implementation status of each algorithm. ..."
Abstract
- Add to MetaCart
Implementation Status The DNS Security Extensions (DNSSEC) requires the use of cryptographic algorithm suites for generating digital signatures over DNS data. There is currently an IANA registry for these algorithms, but there is no record of the recommended implementation status of each algorithm. This document provides an applicability statement on algorithm implementation status for DNSSEC component software. This document lists each algorithm’s status based on the current reference. In the case that an algorithm is specified without an implementation status, this document assigns one. This document
Results 1 - 10
of
743,372
