Bienvenue sur le site internet du GIP RENATER

IPv6 launch Day - 6/06/2012 - et après ...

Plus de détails sur cette journée de lancement mondial d'IPv6 organisée par l'Internet Society dans le cadre de son programme de promotion d'IPv6.

Un ensemble important de mesures et d'observations ont été réalisées par divers organismes lors de cet évènement planétaire et sont poursuivies depuis. Notamment :

sur le site de l'Internet Society
celui du RIPE Labs
et de son equivalent en Asie/Pacifique, APNIC Labs

IPv6 Day

Contexte

Depuis plus de 10 ans, des experts travaillent à une nouvelle version du protocole IP afin de répondre -entre autres- au besoin croissant d'adresses. Le 3 Février dernier, l''Internet Assigned Number Authority (IANA) a procédé à la distribution de ses cinq derniers blocs (/8) d'adresses IPv4 aux Registres Régionaux de l'Internet (RIRs), selon les règles préétablies. Les prévisions permettent d'affirmer que dès cette année, certains registres commenceront à manquer d'adresses IPv4 à attribuer à leurs clients. Le déploiement d'IPv6, pour assurer la continuité des activités de l'Internet, est donc incontournable.

De quoi s'agit il ?

version anglaise de l'évènement

Les principaux fournisseurs de contenus de l'Internet que sont Google, Facebook, Yahoo !, Akamai et Limelight Networks ont décidé d'offrir l'accès à leurs informations en IPv6 pendant 24 heures. L'objectif de cette journée de tests est d'inciter le secteur industriel - prestataires de services, équipementiers, éditeurs de logiciels et hébergeurs de sites web- à se préparer à une transition réussie à IPv6.

Cette initiative, coordonnée par l'Internet Society, a été adoptée par de nombreuses sociétés commerciales, qui ont manifesté leur intérêt pour cet 'IPv6 Day'. cf. http://www.worldipv6day.org/participants/index.html

Concrètement, que faire ?

Pour tout un chacun, il s'agit de vérifier à son niveau de quelle connectivité IPv6 il dispose, mais seuls les opérateurs de réseaux et les gérants de site web sont directement concernés : il s'agit de rendre leurs services compatibles IPv6, c'est à dire de permettre à leurs usagers / clients d'accéder à leurs informations habituelles en utilisant cette nouvelle version du protocole IP. Les administrateurs de sites web qui souhaitent prendre part à cette journée de tests IPv6 peuvent se faire enregistrer sur la page maintenue à jour par l'ISOC.

Et RENATER, dans tout ça ?

Le réseau RENATER est compatible IPv6 depuis 2003, ce n'est plus un secret pour personne ... et a été depuis longtemps leader en matière de promotion d'IPv6.

A l'occasion de cet 'IPv6 Day', nous avons rassemblé ici quelques informations disséminées en de multiples pages du site, et qui pourraient aider ceux qui veulent en profiter pour vérifier quelques 'menus' détails quant à leur degré de préparation pour communiquer demain avec des sites qui ne disposeraient que d'IPv6 (pays asiatiques, africains, ...)

Rappelons que pour les aspects pratiques d'accès aux services IPv6 de RENATER, le contact est l'alias de messagerie support-reseau renater.fr.

Formation et Bibliographie IPv6

Formations CiRen : la prochaine est prévue à l'automne 2011, mais les demandes peuvent être formulées au fil de l'eau pour identifier les besoins en postant un mail à ciren at renater . fr

Formations 6DEPLOY : le contrat européen organise des formations (dans plusieurs langues, dont le français) depuis près de 5 ans. On peut consulter le calendrier
et surtout les modules de formation à IPv6 ainsi qu'un module d'e-learning (le tout en anglais).

Quelques RFCs pour commencer

et un complément plus fraichement publié (avec des résumés en français)

Le livre « IPv6 Théorie et Pratique » en ligne ! proposé par le G6 (groupe d'experts IPv6 de la communauté E&R)

et le Passeport pour l'Internet du futur, publié par l'AFNIC à l'occasion de l'IPv6 Day

Questions sur ces pages, suggestions, compléments : écrire à Bernard .Tuy at renater.fr

Témoignages

Hervé Prigent
Directeur du CRIHAN

Quand avez vous commencé à vous intéresser à IPv6 ?

« Dès le début, c'est-à-dire lors des appels à proposition pour l'évolution d'IP ( »IPng« ). »

Quelle a été la démarche adoptée pour déployer le service IPv6 ?

La démarche a consisté :

à déployer IPv6 sur l'épine dorsale régionale (SYRHANO) et de 'v6fier' les services applicatifs.
à systématiquement demander un support d'IPv6 dans les consultations d'achat des équipements ou des services réseau.
à former nos utilisateurs, par de multiples sessions de formation au CRIHAN, tant théoriques que pratiques. Comme les techniques dites de « migration » ont évolué au fil des ans, il a fallu revoir notre programme de formation régulièrement.

Notre principal problème concernant la sensibilisation et la formation de nos utilisateurs ou partenaires a été que nous envisagions une migration à IPv6 alors qu'eux débutaient avec le protocole IP, qu'ils étaient confrontés à nombre de problèmes (mauvaise utilisation d'IPv4 à cause d'une base technique insuffisante, des problèmes culturels ou autres). Cela est d'ailleurs toujours le cas aujourd'hui...

Qu'apporte IPv6 à vos utilisateurs ?

La pérennité des services.
Des fonctionnalités intéressantes, par exemple dans le domaine de la configuration automatique des équipements.
Une occasion de se poser les bonnes questions et de remettre en cause la culture IPv4, qui est parfois faite de dévoiements technologiques (NAT en est un bel exemple).

Marc FRADIN - Direction Informatique et Système d'Information
IT-Telecom Bretagne

• Depuis combien de temps vous intéressez vous au nouveau protocole IPv6 ?

En tant qu'école de télécom nous avons un rôle « d'évangélisation » de ce protocole (participation au groupe G6 + livre IPv6) pour plus d'informations : http://www.point6.net/

• quelle a été votre action pour en faciliter le déploiement ?

Nous avons été le point de concentration IPv6 en Bretagne pour RENATER durant plusieurs années grâce à des tunnels IPv6 dans IPv4.

Nous avons déployé le protocole sur nos réseaux de production fin des années 1990 et les premiers services (web, messagerie ...) au début des années 2000
Aujourd'hui nous avons activé ipv6 sur presque tous nos réseaux.

Nous avons un peu « essuyé les plâtres »
Nous avons rencontré beaucoup de problèmes avec les constructeurs pour assurer la compatibilité (nous avons identifié beaucoup de bugs !), particulièrement sur les équipements WIFI.

Conseils aux futurs « déployeurs » : bien tester les équipements AVANT de les mettre en production. _Encore pas mal d'effets de bord dûs à un manque de fonctionnalité de sécurité IPv6 sur le réseau local, exemple : détecter les fausses annonces de routeurs IPv6, « Rogue IPv6 Router Advertisement Snooping »

• Qu'apporte IPv6 à vos utilisateurs ?

Pour être honnête IPv6 n'apporte pas grand-chose aux utilisateurs et encore moins aux administrateurs réseaux .... pour l'instant !
Il apporte beaucoup à nos étudiants pour ses vertus pédagogiques.

Déploiement IPv6 sur RENATER

Le service IPv6 unicast est disponible sur RENATER en mode natif depuis 2003.
Tous les routeurs de RENATER sont en double pile IPv4 et IPv6 (« dual stack »).
Des raccordements avec GEANT et avec un opérateur de transit IP permettent d'avoir de la connectivité IPv6 avec la communauté enseignement recherche internationale et plus généralement avec l'Internet IPv6 mondial.

Le GIP RENATER en tant que LIR (Local Internet Registry) s'est vu allouer des blocs d'adresses par le RIPE NCC et de ce fait peut allouer des préfixes IPv4 et IPv6 à sa communauté.

A ce jour, RENATER a alloué :
- 160 préfixes IPv6 (de taille /48)
- 28 préfixes IPv6 pour des réseaux de collecte
- 145 préfixes IPv6 ont été validés avec une demande de routage faite au NOC
- 98 préfixes sont réellement utilisés (annoncé par les sites)

La métrologie IPv6 en temps réel
- depuis le portail des statistiques réseau ou directement depuis ce lien

IPv6 en Europe

EUROPEAN RESEARCH NETWORKS READY FOR IPv6 FUTURE

40 million researchers benefit from early compliance with national and international deployments

Cambridge, UK 1 June 2011 – Research networks across Europe today announced that they have successfully deployed the IPv6 protocol, the next generation of internet addressing technology. Working with network co-ordination centre Réseaux IP Européens (RIPE), research networks have achieved IPv6 compliance and will be taking a leading part in next week's World IPv6 Day (8 June 2011), which tests IPv6 compatibility.

The phenomenal global growth of the internet is leading to a shortage of internet addresses under the existing IPv4 protocol, which will stop new devices being connected in the near future. IPv6 provides enough addresses (340 trillion) to allow the internet to continue to expand and the industry to innovate. It is not, however, directly compatible with IPv4, meaning that devices and networks need to be upgraded to allow IPv6 connections.

“Research networks have always been at the forefront of innovation, not only providing leading edge services to users but acting as a proving ground for new technology, with the IPv6 protocol a perfect example,” said Matthew Scott, General Manager of DANTE, the organisation which on behalf of Europe's National Research and Education Networks (NRENs) has built and operates the GÉANT network. “The shortage of internet addresses under IPv4 is a very real and pressing problem, but thanks to the efforts of Europe's research and education networks vital projects and international collaboration will continue and expand under IPv6.”

The latest European research networks, such as the high speed GÉANT pan-European network have been built from the outset on the IPv6 protocol, and acted as an early test-bed for the technology. NRENs in Finland (Funet), France (RENATER), Ireland (HEAnet), Italy (GARR), Luxembourg (RESTENA), Norway (UNINETT), Portugal (FCCN) and Slovenia (ARNES) have all highlighted their capabilities ahead of World IPv6 Day.

EUROPE – GÉANT
The GÉANT pan-European network has been running ‘native' IPv6 since 2002, and multicast IPv6 since 2004. The experience gained from testing and implementing IPv6 on GÉANT has also been valuable to several other research projects dedicated to developing IPv6. http://www.geant.net/

FINLAND
Funet, the Finnish University and Research Network, has been running IPv6 in production since 2003. Funet is a dual-stack network, supporting IPv4 and IPv6 access everywhere. All basic network services such as DNS and NTP have full IPv6 support. Additionally, Funet runs several transitional services to facilitate the adoption of IPv6. A project skeleton to facilitate the organising of campus transition activities has been created in close collaboration with Funet member organisations. http://www.csc.fi/english

FRANCE
French NREN RENATER provides IPv4 and IPv6 connectivity services - in native mode since 2003. RENATER most frequently connects campus or research centres sites via regional or metropolitan networks of which nearly a third currently support the IPv6 protocol. Visualisation tools, like the IPv6 Weather Map (introduced in February 2009) are available on the RENATER web site. In addition to unicast, RENATER provides a multicast service in native mode for both versions of the IP protocol (IPv4 and IPv6) mainly for video retransmissions. RENATER has been a partner in a number of European programmes including 6NET, 6CHOICE and 6DISS. Currently it is part of the 6DEPLOY-2 programme which aims to install a set of IPv6 test-beds in different continents. Additionally, extensive training material has been created and is kept up-to-date for practical training sessions on IPv6 deployment and management. http://www.renater.fr/

IRELAND
HEAnet, Ireland's NREN, has been running IPv6 in production on all public services since 2003. It is currently in the middle of a three-part strategy to work towards a stable transition. Firstly, managing remaining IPv4 usage, then preparing a full IPv6-only service that interoperates with the IPv4 internet, and thirdly assisting clients and partners in the transition. http://www.heanet.ie/

ITALY
Students and researchers will soon be able to use the eduroam roaming service to connect through IPv6 to the rest of the world from public gardens, parks, archaeological sites and major squares all around Rome and its surroundings, thanks to a joint project carried out by Province of Rome, GARR (the Italian NREN) and CASPUR, a major Italian supercomputing Inter-University Consortium. The Province of Rome has created ProvinciaWiFi, a widespread wireless network with more than 700 hotspots, covering open spaces all around the city and the surrounding province, as well as being available in libraries, cafés, restaurants and other public places. Previously citizens and tourists needed to register in order to access the network, but now students and researchers will be able to just open their laptop and log on thanks to the implementation of eduroam. Extensive tests have been successfully carried out, both in IPv4 and IPv6 over the last few months with the operational phase due to start in June 2011. www.garr.it

LUXEMBOURG
The production use of IPv6 inside Luxembourg NREN RESTENA began by enabling dual-stack on the backbone network in 2003. From then onwards, IPv6 was subsequently introduced into RESTENA's service portfolio and through international peerings to achieve complete integration. IPv6 is available for virtually all customer edge networks in a true dual-stack setup. To guarantee a smooth transition dual-stack user connectivity is based on an opt-in basis. IPv4 and IPv6 are both equally integrated into RESTENA's work-flow, with full transparency from the user perspective. An overview of RESTENA's work is available at http://www.restena.lu/restena/en/EN...

NORWAY
UNINETT have been IPv6 compliant since 1998 and has offered IPv6 to its customers since 2005. Currently 62 per cent of the higher education institutions in Norway are IPv6 enabled, with 49 per cent of the clients at university colleges running IPv6. More information is available at https://ow.feide.no/gigacampus:ipv6...

PORTUGAL.
FCCN, the Portuguese NREN, was one of the first European NRENs to natively connect to GÉANT over IPv6 in 2003. Since then FCCN has been driving its members to deliver their basic internet services over IPv6, including web content, DNS and email services. FCCN has developed two national projects focused on IPv6 and presented at several conferences, including the TERENA Networking Conference. FCCN has also been involved in successful EC sponsored projects like 6NET, 6DISS and 6DEPLOY and is currently participating in 6DEPLOY-2. www.fccn.pt

SLOVENIA
ARNES is one of the earliest adopters of IPv6 in Europe. A step-by-step, long term approach was chosen to deploy IPv6 into the national backbone and services, beginning with the first IPv6 Land Speed Record in 2002 when GÉANT was piloting IPv6 connectivity. Today the ARNES backbone is IPv6 ready. Most services, with the exception of email, are offered to ARNES members over IPv6. ARNES is actively collaborating with the Go6 - Slovenian IPv6 initiative, particularly in organising Slovenian IPv6 summits, conferences, technical workshops as well as providing an active contribution to IPv6 deployment strategy on the national scale, focusing on education and promotion. Recommendations and best practice documents are being prepared to ensure a smooth deployment of IPv6 for ARNES members. ARNES will also take an active part in the World IPv6 Day in Slovenia. www.arnes.si

About GÉANT
GÉANT is the high speed European communication network dedicated to research and education. In combination with its NREN partners, GÉANT creates a secure, high speed research infrastructure that serves 40 million researchers in over 8,000 institutions across 40 European countries. Operating at speeds of up to 40 Gbps, GÉANT is the world's largest and most advanced multi-gigabit network dedicated to research and education. Building on the success of its predecessors, GÉANT has been created around the needs of users, providing flexible, end to end services that transform the way that researchers collaborate. GÉANT is at the heart of global research networking through wide ranging connections with other world regions, underpinning vital projects that bridge the digital divide and benefit society as a whole.

Co-funded by the European Commission under the EU's 7th Research and Development Framework Programme, GÉANT is the e-Infrastructure at the heart of the EU's European Research Area and contributes to the development of emerging internet technologies. The project partners are 32 European National Research and Education Networks (NRENs), TERENA and DANTE. GÉANT is operated by DANTE on behalf of Europe's NRENs. For more information, visit www.GÉANT.net

About DANTE
DANTE is a non-profit organisation, coordinator of large-scale projects co-funded by the European Commission, and working in partnership with European National Research and Education Networks (NRENs) to plan, build and operate advanced networks for research and education. Established in 1993, DANTE has been fundamental to the success of pan-European research and education networking. DANTE has built and operates GÉANT, which provides the data communications infrastructure essential to the success of many research projects in Europe. DANTE is involved in worldwide initiatives to interconnect countries in the other regions to one another and to GÉANT. DANTE currently manages projects focussed on the Mediterranean, Asia-Pacific and central Asia regions through the EUMEDCONNECT, TEIN and CAREN projects respectively. For more information, visit www.dante.net.

Contact :
Paul Maurice
DANTE
+44 (0)1223 371 300
paul.maurice dante.net

RFC et Livres - Métrologie & Mesures de Performances

RFCs

N° du RFC	Intitulé	Date de Publication	Catégorie du RFC
RFC 2330	Framework for IP Performance Metrics	Mai 1998	INFORMATIONAL
RFC 2678	IPPM Metrics for Measuring Connectivity	Septembre 1999	PROPOSED STANDARD
RFC 3393	IP Packet Delay Variation metric for IPPM	Novembre 2002	PROPOSED STANDARD
RFC 3550	RTP : A Transport Protocol for Real-Time Applications	Juillet 2003	PROPOSED STANDARD
RFC 4148	IP Performance Metrics (IPPM) Metrics Registry	Août 2005	Best Current Practice
RFC 4594	Configuration Guidelines for DiffServ Service Classes	Août 2006	INFORMATIONAL
RFC 4656	OWAMP : A One-way Active Measurement Protocol	Septembre 2006	PROPOSED STANDARD
RFC 5166	Metrics for the Evaluation of Congestion Control Mechanisms	Mars 2008	INFORMATIONAL

Livres

Network Management : Accounting & Performance Strategies.
Benoit CLAISE & Ralf WOLTER, Cisco Press, 06/2007

Présentation de l'ouvrage

Document de référence : ToIP / VoIP et technologies voisines

Regroupement dans cette page des documents de référence dans le domaine de la Voix et de la Téléphonie sur IP

Documents de synthèse

document de synthèse sur le déploiement de solutions ToIP : Rédigé par le groupe de réflexion sur la ToIP. Ce groupe était composé d'organismes Education/Recherche en France (2008).

SIP et consorts

N° du RFC	Titre	Date de Publication	Catégorie du RFC
RFC 3261	SIP : Session Initiation Protocol	Juin 2002	PROPOSED STANDARD
ID-16	TURN : Traversal using Relay Around NATs	Juillet 2009	DRAFT
RFC 5389	STUN : Simple Traversal of UDP over NATs	Octobre 2008	PROPOSED STANDARD
[ID-19] -> http://tools.ietf.org/html/draft-ie...]	ICE : Interactive Connectivity Establishment	Octobre 2007	DRAFT

ENUM

N° du RFC	Titre	Date de Publication	Catégorie du RFC
RFC 3761	The E.164 to Uniform Resource Identifiers (URI) Dynamic Delegation Discovery System (DDDS) Application (ENUM)	Avril 2004	PROPOSED STANDARD

Livres sur IPv6

IPv6 for All, a guide for IPv6 usage and application in different environments
Guillermo Cicileo et al.

154 pages

Internet Society, chapter of Argentina, Ed.

The Second Internet
Reinventing Computer Networking with IPv6

Lawrence E. Hughes

306 Pages

Publisher : InfoWeapons

Unit 801, Skyrise Bldg #3, AsiaTown IT Park, Lahug, Cebu City, Cebu 6000
PHILIPPINES - 7/1/2010

IPv6, théorie et pratique
Cet ouvrage est accessible en ligne en suivant le lien ci-dessus. Il est en cours de révision pour y inclure les évolutions récentes.

Gisele Cizault (ouvrage collectif du G6)

O'Reilly - Paris, 11/2005 (quatrième édition)

RFC - Technologies optiques et plans de contrôle

MPLS

RFC	Titre	Auteurs	Date	Statut
5332	MPLS Multicast Encapsulations	T. Eckert, E. Rosen, Ed., R. Aggarwal, Y. Rekhter	August 2008	Updates RFC3032, RFC4023 / PROPOSED STANDARD
5331	MPLS Upstream Label Assignment and Context-Specific Label Space	R. Aggarwal, Y. Rekhter, E. Rosen	August 2008	PROPOSED STANDARD
5283	LDP Extension for Inter-Area Label Switched Paths (LSPs)	B. Decraene, JL. Le Roux, I. Minei	July 2008	PROPOSED STANDARD
5129	Explicit Congestion Marking in MPLS	B. Davie, B. Briscoe, J. Tay	January 2008	PROPOSED STANDARD
4950	ICMP Extensions for Multiprotocol Label Switching R. Bonica, D. Gan, D. Tappan, C. Pignataro	August 2007	PROPOSED STANDARD
4929	Change Process for Multiprotocol Label Switching (MPLS) and Generalized MPLS (GMPLS) Protocols and Procedures	L. Andersson, Ed., A. Farrel, Ed.	June 2007	BEST CURRENT PRACTICE
4906	Transport of Layer 2 Frames Over MPLS	L. Martini, Ed., E. Rosen, Ed., N. El-Aawar, Ed.	June 2007	HISTORIC
4905	Encapsulation Methods for Transport of Layer 2 Frames over MPLS Networks	L. Martini, Ed., E. Rosen, Ed., N. El-Aawar, Ed.	June 2007	HISTORIC
4798	Connecting IPv6 Islands over IPv4 MPLS Using IPv6 Provider Edge Routers (6PE)	J. De Clercq, D. Ooms, S. Prevost, F. Le Faucheur	February 2007	PROPOSED STANDARD
4687	Operations and Management (OAM) Requirements for Point-to-Multipoint MPLS Networks	S. Yasukawa, A. Farrel, D. King, T. Nadeau	September 2006	INFORMATIONAL
4448	Encapsulation Methods for Transport of Ethernet over MPLS Networks	L. Martini, Ed., E. Rosen, N. El-Aawar, G. Heron	April 2006	PROPOSED STANDARD
4368	Multiprotocol Label Switching (MPLS) Label-Controlled Asynchronous Transfer Mode (ATM) and Frame-Relay Management Interface Definition	T. Nadeau, S. Hegde	January 2006	PROPOSED STANDARD
4247	Requirements for Header Compression over MPLS	J. Ash, B. Goode, J. Hand, R. Zhang	November 2005	INFORMATIONAL
4182	Removing a Restriction on the use of MPLS Explicit NULL	E. Rosen	September 2005	Updates RFC3032 / PROPOSED STANDARD
4023	Encapsulating MPLS in IP or Generic Routing Encapsulation (GRE)	T. Worster, Y. Rekhter, E. Rosen	March 2005	PROPOSED STANDARD
3468	The Multiprotocol Label Switching (MPLS) Working Group decision on MPLS signaling protocols	L. Andersson, G. Swallow	February 2003	Updates RFC3212, RFC3472, RFC3475, RFC3476 / INFORMATIONAL
3443	Time To Live (TTL) Processing in Multi-Protocol Label Switching (MPLS) Networks	P. Agarwal, B. Akyol	January 2003	Updates RFC3032 / PROPOSED STANDARD
3429	Assignment of the 'OAM Alert Label' for Multiprotocol Label Switching Architecture (MPLS) Operation and Maintenance (OAM) Functions	H. Ohta	November 2002	INFORMATIONAL
3353	Overview of IP Multicast in a Multi-Protocol Label Switching (MPLS) Environment	D. Ooms, B. Sales, W. Livens, A.Acharya, F. Griffoul, F. Ansari	August 2002	INFORMATIONAL
3063	MPLS Loop Prevention Mechanism	Y. Ohba, Y. Katsube, E. Rosen, P. Doolan	February 2001	EXPERIMENTAL
3034	Use of Label Switching on Frame Relay Networks Specification	A. Conta, P. Doolan, A. Malis	January 2001	PROPOSED STANDARD
3032	MPLS Label Stack Encoding	E. Rosen, D. Tappan, G. Fedorkow, Y. Rekhter, D. Farinacci, T. Li, A. Conta	January 2001	Updated by RFC3443 / PROPOSED STANDARD
3031	Multiprotocol Label Switching Architecture	E. Rosen, A. Viswanathan, R. Callon	January 2001	PROPOSED STANDARD

MPLS-TE

RFC	Titre	Auteurs	Date	Statut
5330	A Link-Type sub-TLV to Convey the Number of Traffic Engineering Label Switched Paths Signalled with Zero Reserved Bandwidth across a Link	JP. Vasseur, Ed., M. Meyer, K. Kumaki, A. Bonda	October 2008	PROPOSED STANDARD
5298	Analysis of Inter-Domain Label Switched Path (LSP) Recovery	T. Takeda, Ed., A. Farrel, Ed., Y. Ikejiri, JP. Vasseur	August 2008	INFORMATIONAL
5152	A Per-Domain Path Computation Method for Establishing Inter-Domain Traffic Engineering (TE) Label Switched Paths (LSPs)	JP. Vasseur, Ed., A. Ayyangar, Ed., R. Zhang	February 2008	PROPOSED STANDARD
4972	Routing Extensions for Discovery of Multiprotocol (MPLS) Label Switch Router (LSR) Traffic Engineering (TE) Mesh Membership	JP. Vasseur, Ed., JL. Leroux, Ed., S. Yasukawa, S. Previdi, P. Psenak, P. Mabbey	July 2007	PROPOSED STANDARD
4829	Label Switched Path (LSP) Preemption Policies for MPLS Traffic Engineering	J. de Oliveira, Ed., JP. Vasseur, Ed., L. Chen, C. Scoglio	April 2007	INFORMATIONAL
4561	Definition of a Record Route Object (RRO) Node-Id Sub-Object	J.-P. Vasseur, Ed., Z. Ali, S. Sivabalan	June 2006	PROPOSED STANDARD
4461	Signaling Requirements for Point-to-Multipoint Traffic-Engineered MPLS Label Switched Paths (LSPs)	S. Yasukawa, Ed.	April 2006	INFORMATIONAL
4216	MPLS Inter-Autonomous System (AS) Traffic Engineering (TE) Requirements	R. Zhang, Ed., J.-P. Vasseur, Ed.	November 2005	INFORMATIONAL
4201	Link Bundling in MPLS Traffic Engineering (TE)	K. Kompella, Y. Rekhter, L. Berger	October 2005	Updates RFC3471, RFC3472, RFC3473 / PROPOSED STANDARD
4128	Bandwidth Constraints Models for Differentiated Services (Diffserv)-aware MPLS Traffic Engineering : Performance Evaluation	W. Lai	June 2005	INFORMATIONAL
4127	Russian Dolls Bandwidth Constraints Model for Diffserv-aware MPLS Traffic Engineering	F. Le Faucheur	June 2005	EXPERIMENTAL
4126	Max Allocation with Reservation Bandwidth Constraints Model for Diffserv-aware MPLS Traffic Engineering & Performance Comparisons	J. Ash	June 2005	EXPERIMENTAL
4125	Maximum Allocation Bandwidth Constraints Model for Diffserv-aware MPLS Traffic Engineering	F. Le Faucheur, W. Lai	June 2005	EXPERIMENTAL
4124	Protocol Extensions for Support of Diffserv-aware MPLS Traffic Engineering	F. Le Faucheur	June 2005	PROPOSED STANDARD
4105	Requirements for Inter-Area MPLS Traffic Engineering	J.-L. Le Roux, J.-P. Vasseur, J. Boyle	June 2005	INFORMATIONAL
4090	Fast Reroute Extensions to RSVP-TE for LSP Tunnels	P. Pan, Ed., G. Swallow, Ed., A. Atlas, Ed.	May 2005	PROPOSED STANDARD
3785	Use of Interior Gateway Protocol (IGP) Metric as a second MPLS Traffic Engineering (TE) Metric	F. Le Faucheur, R. Uppili, A. Vedrenne, P. Merckx, T. Telkamp	May 2004	BEST CURRENT PRACTICE
3564	Requirements for Support of Differentiated Services-aware MPLS Traffic Engineering	F. Le Faucheur, W. Lai	July 2003	INFORMATIONAL
3496	Protocol Extension for Support of Asynchronous Transfer Mode (ATM) Service Class-aware Multiprotocol Label Switching (MPLS) Traffic Engineering	A. G. Malis, T. Hsiao	March 2003	INFORMATIONAL
3469	Framework for Multi-Protocol Label Switching (MPLS)-based Recovery	V. Sharma, F. Hellstrand	February 2003	INFORMATIONAL
3346	Applicability Statement for Traffic Engineering with MPLS	J. Boyle, V. Gill, A. Hannan, D. Cooper, D. Awduche, B. Christian, W.S. Lai	August 2002	INFORMATIONAL
3270	Multi-Protocol Label Switching (MPLS) Support of Differentiated Services	F. Le Faucheur, L. Wu, B. Davie, S. Davari, P.Vaananen, R. Krishnan, P. Cheval, J. Heinanen	May 2002	PROPOSED STANDARD
2702	Requirements for Traffic Engineering Over MPLS	D. Awduche, J. Malcolm, J. Agogbua, M. O'Dell, J. McManus	September 1999	INFORMATIONAL
2430	A Provider Architecture for Differentiated Services and Traffic Engineering (PASTE)	T. Li, Y. Rekhter	October 1998	INFORMATIONAL

LDP et CR-LDP

RFC	Titre	Auteurs	Date	Statut
5283	LDP Extension for Inter-Area Label Switched Paths (LSPs)	B. Decraene, JL. Le Roux, I. Minei	July 2008	PROPOSED STANDARD
5038	The Label Distribution Protocol (LDP) Implementation Survey Results	B. Thomas, L. Andersson	October 2007	INFORMATIONAL
5037	Experience with the Label Distribution Protocol (LDP)	L. Andersson, Ed., I. Minei, Ed., B. Thomas, Ed.	October 2007	INFORMATIONAL
5036	LDP Specification	L. Andersson, Ed., I. Minei, Ed., B. Thomas, Ed	October 2007	Obsoletes RFC 3036/ DRAFT STANDARD
3988	Maximum Transmission Unit Signalling Extensions for the Label Distribution Protocol	B. Black, K. Kompella	January 2005	EXPERIMENTAL
3612	Applicability Statement for Restart Mechanisms for the Label Distribution Protocol (LDP)	A. Farrel	September 2003	INFORMATIONAL
3480	Signalling Unnumbered Links in CR-LDP (Constraint-Routing Label Distribution Protocol)	K. Kompella, Y. Rekhter, A. Kullberg	February 2003	PROPOSED STANDARD
3479	Fault Tolerance for the Label Distribution Protocol (LDP)	A. Farrel	February 2003	PROPOSED STANDARD
3478	Graceful Restart Mechanism for Label Distribution Protocol	M. Leelanivas, Y. Rekhter, R. Aggarwal	February 2003	PROPOSED STANDARD
3215	LDP State Machine	C. Boscher, P. Cheval, L. Wu, E. Gray	January 2002	INFORMATIONAL
3214	LSP Modification Using CR-LDP	J. Ash, Y. Lee, P. Ashwood-Smith, B. Jamoussi, D. Fedyk, D. Skalecki, L. Li	January 2002	PROPOSED STANDARD
3213	Applicability Statement for CR-LDP	J. Ash, M. Girish, E. Gray, B. Jamoussi, G. Wright	January 2002	INFORMATIONAL
3212	Constraint-Based LSP Setup using LDP	B. Jamoussi, Ed., L. Andersson, R. Callon, R. Dantu, L. Wu, P. Doolan, T. Worster, N. Feldman, A. Fredette, M. Girish, E. Gray, J. Heinanen, T. Kilty, A. Malis	January 2002	Updated by RFC3468 / PROPOSED STANDARD
3038	VCID Notification over ATM link for LDP	K. Nagami, Y. Katsube, N. Demizu, H. Esaki, P. Doolan	January 2001	PROPOSED STANDARD
3037	LDP Applicability	B. Thomas, E. Gray	January 2001	INFORMATIONAL
3035	MPLS using LDP and ATM VC Switching	B. Davie, J. Lawrence, K. McCloghrie, E. Rosen, G. Swallow, Y. Rekhter, P. Doolan	January 2001	PROPOSED STANDARD

RSVP et RSVP-TE

RFC	Titre	Auteurs	Date	Statut
5151	Inter-Domain MPLS and GMPLS Traffic Engineering — Resource Reservation Protocol-Traffic Engineering (RSVP-TE) Extensions	A. Farrel, Ed., A. Ayyangar, JP. Vasseur	February 2008	Updates RFC3209, RFC3473 / PROPOSED STANDARD
5063	Extensions to GMPLS Resource Reservation Protocol (RSVP) Graceful Restart	A. Satyanarayana, Ed., R. Rahman, Ed.	October 2007	Updates RFC2961, RFC3473 / PROPOSED STANDARD
4974	Generalized MPLS (GMPLS) RSVP-TE Signaling Extensions in Support of Calls	D. Papadimitriou, A. Farrel	August 2007	Updates RFC3473 / PROPOSED STANDARD
4920	Crankback Signaling Extensions for MPLS and GMPLS RSVP-TE	A. Farrel, Ed., A. Satyanarayana, A. Iwata, N. Fujita, G. Ash	July 2007	PROPOSED STANDARD
4875	Extensions to Resource Reservation Protocol - Traffic Engineering (RSVP-TE) for Point-to-Multipoint TE Label Switched Paths (LSPs)	R. Aggarwal, Ed., D. Papadimitriou, Ed., S. Yasukawa, Ed.	May 2007	PROPOSED STANDARD
4874	Exclude Routes - Extension to Resource ReserVation Protocol-Traffic Engineering (RSVP-TE)	CY. Lee, A. Farrel, S. De Cnodder	April 2007	Updates RFC3209, RFC3473 / PROPOSED STANDARD
4872	RSVP-TE Extensions in Support of End-to-End Generalized Multi-Protocol Label Switching (GMPLS) Recovery	J.P. Lang, Ed., Y. Rekhter, Ed., D. Papadimitriou, Ed.	May 2007	Updates RFC3471, Updated by RFC4873 / PROPOSED STANDARD
4804	Aggregation of Resource ReSerVation Protocol (RSVP) Reservations over MPLS TE/DS-TE Tunnels	F. Le Faucheur, Ed.	February 2007	PROPOSED STANDARD
4420	Encoding of Attributes for Multiprotocol Label Switching (MPLS) Label Switched Path (LSP) Establishment Using Resource ReserVation Protocol-Traffic Engineering (RSVP-TE)	A. Farrel, Ed., D. Papadimitriou, J.-P. Vasseur, A. Ayyangar	February 2006	Updates RFC3209, RFC3473 / PROPOSED STANDARD
3477	Signalling Unnumbered Links in Resource ReSerVation Protocol - Traffic Engineering (RSVP-TE)	K. Kompella, Y. Rekhter	January 2003	PROPOSED STANDARD
3210	Applicability Statement for Extensions to RSVP for LSP-Tunnels	D. Awduche, A. Hannan, X. Xiao	December 2001	INFORMATIONAL
3209	RSVP-TE : Extensions to RSVP for LSP Tunnels	D. Awduche, L. Berger, D. Gan, T. Li, V. Srinivasan, G. Swallow	December 2001	Updated by RFC3936 / PROPOSED STANDARD
2750	RSVP Extensions for Policy Control	S. Herzog	January 2000	Updates RFC2205 / STANDARDS TRACK
2745	RSVP Diagnostic Messages	A. Terzis, B. Braden, S. Vincent, L. Zhang	January 2000	PROPOSED STANDARD
2209	Resource ReSerVation Protocol (RSVP) — Version 1 Message Processing Rules	R. Braden, L. Zhang	September 1997	INFORMATIONAL
2208	Resource ReSerVation Protocol (RSVP) — Version 1 Applicability Statement Some Guidelines on Deployment	A. Mankin, F. Baker, B. Braden, S. Bradner, M. O`Dell, A. Romanow, A. Weinrib, L. Zhang	September 1997	INFORMATIONAL
2205	Resource ReSerVation Protocol (RSVP) — Version 1 Functional Specification	R. Braden, L. Zhang, S. Berson, S. Herzog, S. Jamin	September 1997	Updated by RFC2750, RFC3936 / PROPOSED STANDARD

MPLS VPN

RFC	Titre	Auteurs	Date	Statut
4847	Framework and Requirements for Layer 1 Virtual Private Networks	T. Takeda, Ed.	April 2007	INFORMATIONAL
4797	Use of Provider Edge to Provider Edge (PE-PE) Generic Routing Encapsulation (GRE) or IP in BGP/MPLS IP Virtual Private Networks	Y. Rekhter, R. Bonica, E. Rosen	January 2007	INFORMATIONAL
4577	OSPF as the Provider/Customer Edge Protocol for BGP/MPLS IP Virtual Private Networks (VPNs)	E. Rosen, P. Psenak, P. Pillay-Esnault	June 2006	Updates RFC4364 / PROPOSED STANDARD
4381	Analysis of the Security of BGP/MPLS IP Virtual Private Networks (VPNs)	M. Behringer	February 2006	INFORMATIONAL
4365	Applicability Statement for BGP / MPLS IP Virtual Private Networks (VPNs)	E. Rosen	February 2006	INFORMATIONAL
4364	BGP / MPLS IP Virtual Private Networks (VPNs)	E. Rosen, Y. Rekhter	February 2006	Obsoletes RFC2547, updated by RFC4577 / PROPOSED STANDARD
2917	A Core MPLS IP VPN Architecture	K. Muthukrishnan, A. Malis	September 2000	INFORMATIONAL
2547	BGP/MPLS VPNs	E. Rosen, Y. Rekhter	March 1999	INFORMATIONAL

GMPLS, ASON, O-UNI

RFC	Titre	Auteurs	Date	Statut
5339	Evaluation of Existing GMPLS Protocols against Multi-Layer and Multi-Region Networks (MLN/MRN)	JL. Le Roux, Ed., D. Papadimitriou, Ed.	September 2008	INFORMATIONAL
5307	IS-IS Extensions in Support of Generalized Multi-Protocol Label Switching (GMPLS)	K. Kompella, Ed., Y. Rekhter, Ed.	October 2008	Obsoletes RFC4205, Updates RFC5305 / PROPOSED STANDARD
5212	Requirements for GMPLS-Based Multi-Region and Multi-Layer Networks (MRN/MLN)	K. Shiomoto, D. Papadimitriou, JL. Le Roux, M. Vigoureux, D. Brungard	July 2008	INFORMATIONAL
5150	Label Switched Path Stitching with Generalized Multiprotocol Label Switching Traffic Engineering (GMPLS TE)	A. Ayyangar, K. Kompella, JP. Vasseur, A. Farrel	February 2008	PROPOSED STANDARD
5146	Interworking Requirements to Support Operation of MPLS-TE over GMPLS Networks	K. Kumaki, Ed.	March 2008	INFORMATIONAL
5145	Framework for MPLS-TE to GMPLS Migration	K. Shiomoto, Ed.	March 2008	INFORMATIONAL
4990	Use of Addresses in Generalized Multiprotocol Label Switching (GMPLS) Networks	K. Shiomoto, R. Papneja, R. Rabbat	September 2007	INFORMATIONAL
4929	Change Process for Multiprotocol Label Switching (MPLS) and Generalized MPLS (GMPLS) Protocols and Procedures	L. Andersson, Ed., A. Farrel, Ed.	June 2007	BEST CURRENT PRACTICE
4873	GMPLS Segment Recovery	L. Berger, I. Bryskin, D. Papadimitriou, A. Farrel	May 2007	Updates RFC3473, RFC4872 / PROPOSED STANDARD
4606	Generalized Multi-Protocol Label Switching (GMPLS) Extensions for Synchronous Optical Network (SONET) and Synchronous Digital Hierarchy (SDH) Control	E. Mannie, D. Papadimitriou	August 2006	Obsoletes RFC3946 / PROPOSED STANDARD
4428	Analysis of Generalized Multi-Protocol Label Switching (GMPLS)-based Recovery Mechanisms (including Protection and Restoration)	D. Papadimitriou, Ed., E. Mannie, Ed.	March 2006	INFORMATIONAL
4427	Recovery (Protection and Restoration) Terminology for Generalized Multi-Protocol Label Switching (GMPLS)	E. Mannie, Ed., D. Papadimitriou, Ed.	March 2006	INFORMATIONAL
4426	Generalized Multi-Protocol Label Switching (GMPLS) Recovery Functional Specification	J. Lang, Ed., B. Rajagopalan, Ed., D. Papadimitriou, Ed.	March 2006	PROPOSED STANDARD
4397	A Lexicography for the Interpretation of Generalized Multiprotocol Label Switching (GMPLS) Terminology within the Context of the ITU-T's Automatically Switched Optical Network (ASON) Architecture	I. Bryskin, A. Farrel	February 2006	INFORMATIONAL
4394	A Transport Network View of the Link Management Protocol (LMP)	D. Fedyk, O. Aboul-Magd, D. Brungard, J. Lang, D. Papadimitriou	February 2006	INFORMATIONAL
4328	Generalized Multi-Protocol Label Switching (GMPLS) Signaling Extensions for G.709 Optical Transport Networks Control	D. Papadimitriou, Ed.	January 2006	Updates RFC3471 / PROPOSED STANDARD
4258	Requirements for Generalized Multi-Protocol Label Switching (GMPLS) Routing for the Automatically Switched Optical Network (ASON)	D. Brungard, Ed.	November 2005	INFORMATIONAL
4209	Link Management Protocol (LMP) for Dense Wavelength Division Multiplexing (DWDM) Optical Line Systems	A. Fredette, Ed., J. Lang, Ed.	October 2005	PROPOSED STANDARD
4208	Generalized Multiprotocol Label Switching (GMPLS) User-Network Interface (UNI) : Resource ReserVation Protocol-Traffic Engineering (RSVP-TE) Support for the Overlay Model	G. Swallow, J. Drake, H. Ishimatsu, Y. Rekhter	October 2005	PROPOSED STANDARD
4207	Synchronous Optical Network (SONET)/Synchronous Digital Hierarchy (SDH) Encoding for Link Management Protocol (LMP) Test Messages	J. Lang, D. Papadimitriou	October 2005	PROPOSED STANDARD
4206	Label Switched Paths (LSP) Hierarchy with Generalized Multi-Protocol Label Switching (GMPLS) Traffic Engineering (TE)	K. Kompella, Y. Rekhter	October 2005	PROPOSED STANDARD
4205	Intermediate System to Intermediate System (IS-IS) Extensions in Support of Generalized Multi-Protocol Label Switching (GMPLS)	K. Kompella, Ed., Y. Rekhter, Ed.	October 2005	Updates RFC3784 / INFORMATIONAL
3471	Generalized Multi-Protocol Label Switching (GMPLS) Signaling Functional Description	L. Berger	January 2003	PROPOSED STANDARD
4204	Link Management Protocol (LMP)	J. Lang, Ed.	October 2005	PROPOSED STANDARD
4203	OSPF Extensions in Support of Generalized Multi-Protocol Label Switching (GMPLS)	K. Kompella, Ed., Y. Rekhter, Ed.	October 2005	Updates RFC3630 / PROPOSED STANDARD
4202	Routing Extensions in Support of Generalized Multi-Protocol Label Switching (GMPLS)	K. Kompella, Ed., Y. Rekhter, Ed.	October 2005	PROPOSED STANDARD
4139	Requirements for Generalized MPLS (GMPLS) Signaling Usage and Extensions for Automatically Switched Optical Network (ASON)	D. Papadimitriou, J. Drake, J. Ash, A. Farrel, L. Ong	July 2005	INFORMATIONAL
4003	GMPLS Signaling Procedure for Egress Control	L. Berger	February 2005	Updates RFC3473 / PROPOSED STANDARD
3946	Generalized Multi-Protocol Label Switching (GMPLS) Extensions for Synchronous Optical Network (SONET) and Synchronous Digital Hierarchy (SDH) Control	E. Mannie, D. Papadimitriou	October 2004	Obsoleted by RFC4606 / PROPOSED STANDARD
3945	Generalized Multi-Protocol Label Switching (GMPLS) Architecture	E. Mannie	October 2004	PROPOSED STANDARD
3476	Documentation of IANA Assignments for Label Distribution Protocol (LDP), Resource ReSerVation Protocol (RSVP), and Resource ReSerVation Protocol-Traffic Engineering (RSVP-TE) Extensions for Optical UNI Signaling	B. Rajagopalan	March 2003	Updated by RFC3468 / INFORMATIONAL
3475	Documentation of IANA assignments for Constraint-Based LSP setup using LDP (CR-LDP) Extensions for Automatic Switched Optical Network (ASON)	O. Aboul-Magd	March 2003	Updated by RFC3468 / INFORMATIONAL
3474	Documentation of IANA assignments for Generalized MultiProtocol Label Switching (GMPLS) Resource Reservation Protocol - Traffic Engineering (RSVP-TE) Usage and Extensions for Automatically Switched Optical Network (ASON)	Z. Lin, D. Pendarakis	March 2003	INFORMATIONAL
3473	Generalized Multi-Protocol Label Switching (GMPLS) Signaling Resource ReserVation Protocol-Traffic Engineering (RSVP-TE) Extensions	L. Berger	January 2003	Updated by RFC4003 / PROPOSED STANDARD
3472	Generalized Multi-Protocol Label Switching (GMPLS) Signaling Constraint-based Routed Label Distribution Protocol (CR-LDP) Extensions	P. Ashwood-Smith, L. Berger	January 2003	Updated by RFC3468 / PROPOSED STANDARD

Path Computation Element

RFC	Titre	Auteurs	Date	Statut	Résumé
5376	Inter-AS Requirements for the Path Computation Element Communication Protocol (PCECP)	N. Bitar, R. Zhang, K. Kumaki	November 2008	INFORMATIONAL

Layer 1 VPN

RFC	Titre	Auteurs	Date	Statut
5253	Applicability Statement for Layer 1 Virtual Private Network (L1VPN) Basic Mode	T. Takeda, Ed.	July 2008	INFORMATIONAL
5252	OSPF-Based Layer 1 VPN Auto-Discovery	I. Bryskin, L. Berger	July 2008	PROPOSED STANDARD
5251	Layer 1 VPN Basic Mode	D. Fedyk, Ed., Y. Rekhter, Ed., D. Papadimitriou, R. Rabbat, L. Berger	July 2008	PROPOSED STANDARD
5195	BGP-Based Auto-Discovery for Layer-1 VPNs	H. Ould-Brahim, D. Fedyk, Y. Rekhter	June 2008	PROPOSED STANDARD

MIB

RFC	Titre	Auteurs	Date	Statut
4803	Generalized Multiprotocol Label Switching (GMPLS) Label Switching Router (LSR) Management Information Base	T. Nadeau, Ed., A. Farrel, Ed.	February 2007	PROPOSED STANDARD
4802	Generalized Multiprotocol Label Switching (GMPLS) Traffic Engineering Management Information Base	T. Nadeau, Ed., A. Farrel, Ed.	February 2007	PROPOSED STANDARD
4801	Definitions of Textual Conventions for Generalized Multiprotocol Label Switching (GMPLS) Management	T. Nadeau, Ed., A. Farrel, Ed.	February 2007	PROPOSED STANDARD
4382	MPLS/BGP Layer 3 Virtual Private Network (VPN) Management Information Base	T. Nadeau, Ed., H. van der Linde, Ed.	February 2006	PROPOSED STANDARD
4379	Detecting Multi-Protocol Label Switched (MPLS) Data Plane Failures	K. Kompella, G. Swallow	February 2006	Updates RFC1122 / PROPOSED STANDARD
4378	A Framework for Multi-Protocol Label Switching (MPLS) Operations and Management (OAM)	D. Allan, Ed., T. Nadeau, Ed.	February 2006	INFORMATIONAL
4377	Operations and Management (OAM) Requirements for Multi-Protocol Label Switched (MPLS) Networks	T. Nadeau, M. Morrow, G. Swallow, D. Allan, S. Matsushima	February 2006	INFORMATIONAL
4327	Link Management Protocol (LMP) Management Information Base (MIB)	M. Dubuc, T. Nadeau, J. Lang, E. McGinnis	January 2006	PROPOSED STANDARD
4220	Traffic Engineering Link Management Information Base	M. Dubuc, T. Nadeau, J. Lang	November 2005	PROPOSED STANDARD
3919	Remote Network Monitoring (RMON) Protocol Identifiers for IPv6 and Multi Protocol Label Switching (MPLS)	E. Stephan, J. Palet	October 2004	INFORMATIONAL
3815	Definitions of Managed Objects for the Multiprotocol Label Switching (MPLS), Label Distribution Protocol (LDP)	J.Cucchiara, H. Sjostrand, J. Luciani	June 2004	PROPOSED STANDARD
3814	Multiprotocol Label Switching (MPLS) Forwarding Equivalence Class To Next Hop Label Forwarding Entry (FEC-To-NHLFE) Management Information Base (MIB)	T. Nadeau, C. Srinivasan, A. Viswanathan	June 2004	PROPOSED STANDARD
3813	Multiprotocol Label Switching (MPLS) Label Switching Router (LSR) Management Information Base (MIB)	C. Srinivasan, A. Viswanathan, T. Nadeau	June 2004	PROPOSED STANDARD
3812	Multiprotocol Label Switching (MPLS) Traffic Engineering (TE) Management Information Base (MIB)	C. Srinivasan, A. Viswanathan, T. Nadeau	June 2004	PROPOSED STANDARD
3811	Definitions of Textual Conventions (TCs) for Multiprotocol Label Switching (MPLS) Management	T. Nadeau, J. Cucchiara	June 2004	PROPOSED STANDARD
3592	Definitions of Managed Objects for the Synchronous Optical Network/Synchronous Digital Hierarchy (SONET/SDH) Interface Type	K. Tesink	September 2003	Obsoletes RFC2558 / DRAFT STANDARD
3591	Definitions of Managed Objects for the Optical Interface Type	H-K. Lam, M. Stewart, A. Huynh	September 2003	PROPOSED STANDARD

Interfaces optiques

RFC	Titre	Auteurs	Date	Statut
4837	Managed Objects of Ethernet Passive Optical Networks (EPON)	L. Khermosh	July 2007	PROPOSED STANDARD
4054	Impairments and Other Constraints on Optical Layer Routing	J. Strand, Ed., A. Chiu, Ed.	May 2005	INFORMATIONAL
3717	IP over Optical Networks : A Framework	B. Rajagopalan, J. Luciani, D. Awduche	March 2004	INFORMATIONAL
3604	Requirements for Adding Optical Support to the General Switch Management Protocol version 3 (GSMPv3)	H. Khosravi, G. Kullgren, S. Shew, J. Sadler, A. Watanabe	October 2003	INFORMATIONAL

SDH

RFC	Titre	Auteurs	Date	Statut	Résumé
3255	Extending Point-to-Point Protocol (PPP) over Synchronous Optical NETwork/Synchronous Digital Hierarchy (SONET/SDH) with virtual concatenation, high order and low order payloads	N. Jones, C. Murton	April 2002	PROPOSED STANDARD
2615	PPP over SONET/SDH	A. Malis, W. Simpson	June 1999	Obsoletes RFC1619 / PROPOSED STANDARD

RFC - Multicast

Définitions et adressage

RFC	Titre	Auteurs	Date	Statut
1112	Host Extensions for IP Multicasting	S. Deering	August 1989	Obsoletes RFCs 988, 1054, Updated by RFC2236 / RECOMMENDED STANDARD
1546	Host Anycasting Service	C. Partridge, T. Mendez, W. Milliken	November 1993	INFORMATIONAL
2373	IP Version 6 Addressing Architecture	R. Hinden, S. Deering	July 1998	Obsoletes RFC1884 / PROPOSED STANDARD
2375	IPv6 Multicast Address Assignments	R. Hinden, S. Deering	July 1998	INFORMATIONAL

Gestion des groupes de diffusion

RFC	Titre	Auteurs	Date	Statut	Résumé
2710	Multicast Listener Discovery (MLD) for IPv6	S. Deering, W. Fenner, B. Haberman	October 1999	PROPOSED STANDARD
3810	Multicast Listener Discovery Version 2 (MLDv2) for IPv6	R. Vida, L. Costa	June 2004	PROPOSED STANDARD

Routage multicast et construction d'arbres multicast

RFC	Titre	Auteurs	Date	Statut
1075	Distance Vector Multicast Routing Protocol	D. Waitzman, C. Partridge, S.E. Deering	November 1988	EXPERIMENTAL
1458	Requirements for Multicast Protocols	R. Braudes, S. Zabele	May 1993	INFORMATIONAL
2362	Protocol Independent Multicast-Sparse Mode (PIM-SM) : Protocol Specification	D. Estrin, D. Farinacci, A. Helmy, D. Thaler, S. Deering, M. Handley, V. Jacobson, C. Liu, P. Sharma, L. Wei	June 1998	Obsoletes RFC2117 / EXPERIMENTAL
2715	Interoperability Rules for Multicast Routing Protocols	D.Thaler	October 1999	INFORMATIONAL

Multicast interdomaine

RFC	Titre	Auteurs	Date	Statut	Résumé
3618	Multicast Source Discovery Protocol (MSDP)	B. Fenner, D. Meyer	October 2003	EXPERIMENTAL
3956	Embedding the Rendezvous Point (RP) Address in an IPv6 Multicast Address	P. Savola, B. Haberman	November 2004	PROPOSED STANDARD

Allocation dynamique des adresses multicast

RFC	Titre	Auteurs	Date	Statut
2730	Multicast Address Dynamic Client Allocation Protocol (MADCAP)	S.Hanna, B. Patel, M. Shah	December 1999	PROPOSED STANDARD
2771	An Abstract API for Multicast Address Allocation	R. Finlayson	February 2000	INFORMATIONAL
2776	Multicast-Scope Zone Announcement Protocol (MZAP)	M. Handley, D. Thaler, R. Kermode	February 2000	PROPOSED STANDARD
2907	MADCAP Multicast Scope Nesting State Option	R. Kermode	September 2000	PROPOSED STANDARD
2908	The Internet Multicast Address Allocation Architecture	D. Thaler, M. Handley, D. Estrin	September 2000	INFORMATIONAL

Supervision

RFC	Titre	Auteurs	Date	Statut	Résumé
2417	Definitions of Managed Objects for Multicast over UNI 3.0/3.1 based ATM Networks	C. Chung, M. Greene	September 1998	Obsoletes RFC2366 / PROPOSED STANDARD
3019	IP Version 6 Management Information Base for The Multicast Listener Discovery Protocol	B. Haberman, R. Worzella	January 2001	PROPOSED STANDARD

Sécurité

RFC	Titre	Auteurs	Date	Statut	Résumé
1949	Scalable Multicast Key Distribution	A. Ballardie	May 1996	EXPERIMENTAL
2588	IP Multicast and Firewalls	R. Finlayson	May 1999	INFORMATIONAL

Performances

RFC	Titre	Auteurs	Date	Statut	Résumé
2432	Terminology for IP Multicast Benchmarking	K. Dubray	October 1998	INFORMATIONAL

Applications

RFC	Titre	Auteurs	Date	Statut	Résumé
2090	TFTP Multicast Option	A. Emberson	February 1997	EXPERIMENTAL
3170	IP Multicast Applications : Challenges and Solutions	B. Quinn, K. Almeroth	September 2001	INFORMATIONAL

Multicast VPN

N° du RFC	Titre	Date	Catégorie du document
RFC 4577	OSPF as the Provider/Customer Edge Protocol for BGP/MPLS IP Virtual Private Networks (VPNs)	Juin 2006	PROPOSED STANDARD
RFC 4834	Requirements for Multicast in Layer 3 Provider-Provisioned Virtual Private Networks	Avril 2007	INFORMATIONAL