CHAP (1994)_e Network Working Group W. Simpson Request for Comments: 1994 DayDreamer Obsoletes: 1334 August 1996 Category: Standards Track PPP Challenge Handshake Authentication Protocol (CHAP) Status of this Memo This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. SIP: Session Initiation Protocol Archive Archive for drafts Mailing list archive HTML, through March 1998 All SIP-related drafts SIP-related RFCs: Summary of SIP-Related Standardization Efforts There are a number of extensions for adding features to SIP. Given the number of drafts, it may be hard to track which drafts are significant for different applications. Core SIP Specification The core SIP specification is RFC 3261, which obsoletes RFC 2543. Informational Documents Call Flows To help implementors, a set of call flows has been published that give examples of common call setup and registration scenarios. Guidelines for Writing SIP Extensions A number of extensions are being proposed to add headers or methods to SIP. SIP Through NATs and Firewalls These drafts presents information on issues that arise in getting SIP and related multimedia services through NATs and firewalls. SIP Enabled Services to Support the Hearing Impaired User Agent Configuration Network Management Header Session Timer
comp.lang.c Frequently Asked Questions CHAP (1994)_f Statut de ce document Ce document spécifie un protocole standard d'Internet pour la communauté Internet, et ne sera éprouvé qu'après plusieurs discussions et suggestions. Merci de vous référer à l'édition courante du " Internet Official Protocol Standards " (STD1) pour l'état de standardisation et le statut de ce protocole. Résumé Le Protocole Point à Point (PPP) [1] fournit une méthode standard pour transporter des datagrammes multiprotocoles au-dessus de liens point à point. Le PPP définit également un protocole extensible de contrôle de lien, qui permet la négociation d'un protocole d'authentification pour authentifier son pair avant de permettre à des protocoles de couche réseau de transmettre au-dessus du lien. Ce document définit une méthode pour l'authentification sur PPP, qui utilise un challenge aléatoire, avec une réponse hachée cryptographiquement qui dépend du challenge et d'une clé secrète. Table des matières 1. Par défaut, l'authentification n'est pas obligatoire. Pair 2. 3. 4.
Radius (2865)_e "Remote Authentication Dial In User Service (RADIUS)", June 2000 Canonical URL: document is also available in this non-normative format: PDF. Status: Obsoletes: Updated by: Authors: C. Stream: Source: radius (ops) Cite this RFC: TXT | XML Other actions: Find Errata (if any) | Submit Errata | Find IPR Disclosures from the IETF Abstract This document describes a protocol for carrying authentication, authorization, and configuration information between a Network Access Server which desires to authenticate its links and a shared Authentication Server. For the definition of Status, see RFC 2026. For the definition of Stream, see RFC 4844. Go to the RFC Editor Homepage. FTP Security Extension (2228)_e Network Working Group M. Horowitz Request for Comments: 2228 Cygnus Solutions Updates: 959 S. Lunt Category: Standards Track Bellcore October 1997 FTP Security Extensions Status of this Memo This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited.