Le guide de la
Messagerie Instantanée


l'actualité
les flashs
la chronique
Interviews


choisir son pager
la synthèse
les utilitaires


le chat irc 
le forum
liste de diffusion
Devenez testeur
le pager parfait


premiers pas
personnaliser son pager
mot de passe oublié ?


c'est quoi un pager ?
la sécurité
le protocole IMPP


afficher son status
homepage chat room
web messages

Quoi de neuf

Les liens
Carte du site
recherches


avec FreeFind

A propos de...

IETF En savoir plus...
Pour tout connaitre des RFC, des futures normes de l'internet, etc..
Rendez-vous sur le site de l'IEFT

Comprendre
Un protocole pour quoi faire ?

Vous l'avez sans doute remarqué , la particularité des pagers est d'être (à part quelques exceptions ) incompatible les uns avec les autres. Normal étant donné qu'à l'heure actuelle il n'existe aucun protocole permettant une compatibilité entre les différents produits.

C'est dans ce but que l'Internet Engineering Task Force (IETF) à mis en place un groupe de travail afin de définir les bases du protocole IMPP (Instant Messaging and Presence Protocol).

PS: les informations qui suivent étant très fortement techniques, nous vous les livront en Version Originale afin de ne pas dénaturer le texte par une traduction incorrecte.

L'Internet Engineering Task Force (IETF)

The Internet Engineering Task Force (IETF) is a large open international community of network designers, operators, vendors, and researchers concerned with the evolution of the Internet architecture and the smooth operation of the Internet. It is open to any interested individual.

The actual technical work of the IETF is done in its working groups, which are organized by topic into several areas (e.g., routing, transport, security, etc.). Much of the work is handled via mailing lists. The IETF holds meetings three times per year.

The IETF working groups are grouped into areas, and managed by Area Directors, or ADs. The ADs are members of the Internet Engineering Steering Group (IESG). Providing architectural oversight is the Internet Architecture Board, (IAB). The IAB also adjudicates appeals when someone complains that the IESG has failed. The IAB and IESG are chartered by the Internet Society (ISOC) for these purposes. The General Area Director also serves as the chair of the IESG and of the IETF, and is an ex-officio member of the IAB.

The Internet Assigned Numbers Authority (IANA) is the central coordinator for the assignment of unique parameter values for Internet protocols. The IANA is chartered by the Internet Society (ISOC) to act as the clearinghouse to assign and coordinate the use of numerous Internet protocol parameters.

First-time attendees might find it helpful to read The Tao of the IETF.

Le protocole IMPP

------ Contacts ------
Chair(s):
vj@research.att.com
dave@marvit.org
Applications Area Director(s): moore@cs.utk.edu
paf@swip.net
Applications Area Advisor: paf@swip.net
Mailing Lists:
General Discussion:
impp@iastate.edu
To Subscribe:
impp-request@iastate.edu
Archive:
http://lists.fsck.com/cgi-bin/wilma/pip

Last Modified: 04-Jun-99

Description of Working Group:

This working group will eventually define protocols and data formats necessary to build an internet-scale end-user presence awareness, notification and instant messaging system. Its initial task is to determine specific design goals and requirements for such a service. The design goals document will be submitted for IETF-wide review, and based on that review, the group's charter will be extended.

Background:

Instant messaging differs from email primarily in that its primary focus is immediate end-user delivery. Presence information was readily accessible on internet-connected systems years ago; when a user had an open session to a well-known multi-user system, his friends and colleagues could easily tell where he was connected from and whether he was using his computer. Since that time, computing infrastructure has become increasingly distributed and a given user may be consistently available," but has no standard way to make this information known to her peers. This working group will design a system to address this need.

Goals:

The working group will develop an architecture for simple instant messaging and presence awareness/notification. It will specify how authentication, message integrity, encryption and access control are integrated. It is desirable, but not required, for the working group to develop a solution that works well for awareness of and communication with entities other than human users.

Non-goals:

Providing a general notification mechanism for data other than user presence information and instant messages.

The following keywords describe the scope for the working group. Details are to be developed in the architecture document which is the output of this working group:

  • PRESENCE
  • INSTANT MESSAGING
  • SHARED
  • NAMING
  • AUTHENTICATION
  • ACCESS CONTROL
  • SCALABILITY

Deliverables:

The working group plans to deliver the following document:

- Requirements for Instant Messaging and Presence

Goals and Milestones:

May 99    Submit Internet-Draft of Design Goals for Instant Messaging and Presence Information
Jul 99    Submit design goals Internet-Draft to IESG for publication as an RFC

Internet-Drafts:

A Model for Presence and Instant Messaging (31757 bytes)
Instant Messaging / Presence Protocol Requirements (37651 bytes)


Aussitot, le guide de la messagerie Instantanée - http://www.aussitot.net
webmaster@aussitot.net - © 1999-2000 Aussitot - tous droits réservés
Discutez en direct sur