begin process at 2013 05 25 09:41:21
  Trouver un code source :
 
dans
 

RFC classées sous Nat

RFC
4787
Network Address Translation (NAT) Behavioral Requirements for Unicast UDP

This document defines basic terminology for describing different types of network address translation (nat) behavior when handling unicast udp and also defines a set of requirements that would allow many applications, such as multimedia communicat...
Déposé par Auteur(s) : Editor F. Audet, C. Jennings
Classé sous : Nat, Sip, Udp
RFC
3989
Middlebox Communications (MIDCOM) Protocol Semantics

This memo specifies semantics for a middlebox communication (midcom) protocol to be used by midcom agents for interacting with middleboxes such as firewalls and network address translators (nats). the semantics discussion does not include any spec...
Déposé par Auteur(s) : M. Stiemerling, J. Quittek, T. Taylor
Classé sous : Nat, Network address translator, Firewall
RFC
3605
Real Time Control Protocol (RTCP) attribute in Session Description Protocol (SDP)

The session description protocol (sdp) is used to describe the parameters of media streams used in multimedia sessions. when a session requires multiple ports, sdp assumes that these ports have consecutive numbers. however, when the session crosse...
Déposé par Auteur(s) : C. Huitema
Classé sous : Nat, Network access translation, Port mapping
RFC
3519
Mobile IP Traversal of Network Address Translation (NAT) Devices

Mobile ip's datagram tunnelling is incompatible with network address translation (nat). this document presents extensions to the mobile ip protocol and a tunnelling method which permits mobile nodes using mobile ip to operate in private address ne...
Déposé par Auteur(s) : H. Levkowetz, S. Vaarala
Classé sous : Internet protocol, Datagram, Traffic, Mobile ip, Nat, Napt, Traversal, Tunnelling, Tunneling, Udp, Private address space, Keepalives, Port 434, Mip, Mipv4, Network address translation
RFC
3424
IAB Considerations for UNilateral Self-Address Fixing (UNSAF) Across Network Address Translation

As a result of the nature of network address translation (nat) middleboxes, communicating endpoints that are separated by one or more nats do not know how to refer to themselves using addresses that are valid in the addressing realms of their (cur...
Déposé par Auteur(s) : Editor L. Daigle, IAB
Classé sous : Nat, Middleboxes
RFC
3257
Stream Control Transmission Protocol Applicability Statement

This document describes the applicability of the stream control transmission protocol (sctp). it also contrasts sctp with the two dominant transport protocols, user datagram protocol (udp) & transmission control protocol (tcp), and gives some guid...
Déposé par Auteur(s) : L. Coene
Classé sous : Sctp, Udp, Tcp, Rtp, Transport security, Transport, Nat, Multihoming
RFC
3105
Finding an RSIP Server with SLP

This document contains an slp service type template that describes the advertisements made by rsip servers for their services. this memo defines an experimental protocol for the internet community.
Déposé par Auteur(s) : J. Kempf, G. Montenegro
Classé sous : Realm, Specific, Internet, Protocol, Service, Location, Nat, Addressing, Requirements
RFC
3104
RSIP Support for End-to-end IPsec

This document proposes mechanisms that enable realm specific ip (rsip) to handle end-to-end ipsec (ip security). this memo defines an experimental protocol for the internet community.
Déposé par Auteur(s) : G. Montenegro, M. Borella
Classé sous : Realm, Specific, Internet, Protocol, Nat, Addressing, Requirements
RFC
3103
Realm Specific IP: Protocol Specification

This document presents a protocol with which to implement realm specific ip (rsip). the protocol defined herein allows negotiation of resources between an rsip host and gateway, so that the host can lease some of the gateway's addressing parameter...
Déposé par Auteur(s) : M. Borella, D. Grabelsky, J. Lo, K. Taniguchi
Classé sous : Rsip, Host, Gateway, Nat, Requirements
RFC
3102
Realm Specific IP: Framework

This document examines the general framework of realm specific ip (rsip). rsip is intended as a alternative to nat in which the end-to- end integrity of packets is maintained. we focus on implementation issues, deployment scenarios, and interactio...
Déposé par Auteur(s) : M. Borella, J. Lo, D. Grabelsky, G. Montenegro
Classé sous : Rsip, End-to-end, Nat, Addressing, Requirements


Nos sponsors


Sondage...

Comparez les prix

CalendriCode

Photothèque

A découvrir



 
Développement réalisé par Nicolas SOREL (Nix) avec l'aide de : Cyril DURAND et Emmanuel (EBArtSoft), Merci à Vincent pour ses précieux conseils.
CodeS-SourceS.com© Toute reproduction même partielle est interdite sauf accord écrit du Webmaster
CodeS-SourceS.com© est une marque déposée tous droits réservés

Google Coop CodeS-SourceS Google Coop CodeS-SourceS
Temps d'éxécution de la page : 0,031 sec (3)

Nous contacter | Annoncer sur CodeS-SourceS | Mentions légales