RE: Last Call <draft-sprecher-mpls-tp-oam-considerations-01.txt> (The Reasons for Selecting a Single Solution for MPLS-TP OAM) to Informational RFC

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: John E Drake <jdrake@xxxxxxxxxxx>, Ross Callon <rcallon@xxxxxxxxxxx>, "ietf@xxxxxxxx" <ietf@xxxxxxxx>
Subject: RE: Last Call <draft-sprecher-mpls-tp-oam-considerations-01.txt> (The Reasons for Selecting a Single Solution for MPLS-TP OAM) to Informational RFC
From: Rolf Winter <Rolf.Winter@xxxxxxxxx>
Date: Thu, 13 Oct 2011 06:50:40 +0000
Accept-language: en-US, de-DE
Delivered-to: ietf@xxxxxxxxxxxxxx
In-reply-to: <5E893DB832F57341992548CDBB333163A442E87AED@EMBX01-HQ.jnpr.net>
Thread-index: AQHMh4SlsNDg37erWEmJlfbJr8x6qZV2wLAQgACP6FCAABgxgIAANqhQgAEAFmCAATkvcA==
Thread-topic: Last Call <draft-sprecher-mpls-tp-oam-considerations-01.txt> (The Reasons for Selecting a Single Solution for MPLS-TP OAM) to Informational RFC

> How does the IETF put a big red warning sign on a document produced by
> another standards body?

http://tools.ietf.org/html/draft-bhh-mpls-tp-oam-y1731-07. Actual coloring of course is impossible.

NEC Europe Limited | Registered Office: NEC House, 1 Victoria Road, London W3 6BL | Registered in England 2832014 



_______________________________________________
Ietf mailing list
Ietf@xxxxxxxx
https://www.ietf.org/mailman/listinfo/ietf

References:
- Re: Last Call <draft-sprecher-mpls-tp-oam-considerations-01.txt> (The Reasons for Selecting a Single Solution for MPLS-TP OAM) to Informational RFC
  - From: Stephen Kent
- RE: Last Call <draft-sprecher-mpls-tp-oam-considerations-01.txt> (The Reasons for Selecting a Single Solution for MPLS-TP OAM) to Informational RFC
  - From: Rolf Winter
- RE: Last Call <draft-sprecher-mpls-tp-oam-considerations-01.txt> (The Reasons for Selecting a Single Solution for MPLS-TP OAM) to Informational RFC
  - From: Ross Callon
- RE: Last Call <draft-sprecher-mpls-tp-oam-considerations-01.txt> (The Reasons for Selecting a Single Solution for MPLS-TP OAM) to Informational RFC
  - From: Rolf Winter
- RE: Last Call <draft-sprecher-mpls-tp-oam-considerations-01.txt> (The Reasons for Selecting a Single Solution for MPLS-TP OAM) to Informational RFC
  - From: Ross Callon
- RE: Last Call <draft-sprecher-mpls-tp-oam-considerations-01.txt> (The Reasons for Selecting a Single Solution for MPLS-TP OAM) to Informational RFC
  - From: John E Drake

Prev by Date: Re: size of the XML of IANA ports
Next by Date: Re: size of the XML of IANA ports
Previous by thread: RE: Last Call <draft-sprecher-mpls-tp-oam-considerations-01.txt> (The Reasons for Selecting a Single Solution for MPLS-TP OAM) to Informational RFC
Next by thread: RE: Last Call <draft-sprecher-mpls-tp-oam-considerations-01.txt> (The Reasons for Selecting a Single Solution for MPLS-TP OAM) to Informational RFC
Index(es):
- Date
- Thread

[Index of Archives] [IETF Annoucements] [IETF] [IP Storage] [Yosemite News] [Linux SCTP] [Linux Newbies] [Fedora Users]