RE: Proposed response to OIF on OSPF ENNI
"Ong, Lyndon" <Lyong@Ciena.com> Tue, 25 July 2006 22:28 UTC
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1G5VNj-0004dj-Pb for ccamp-archive@ietf.org; Tue, 25 Jul 2006 18:28:03 -0400
Received: from psg.com ([147.28.0.62]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G5VNi-00010C-3Z for ccamp-archive@ietf.org; Tue, 25 Jul 2006 18:28:03 -0400
Received: from majordom by psg.com with local (Exim 4.60 (FreeBSD)) (envelope-from <owner-ccamp@ops.ietf.org>) id 1G5VJB-0001D8-Go for ccamp-data@psg.com; Tue, 25 Jul 2006 22:23:21 +0000
X-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10) on psg.com
X-Spam-Level:
X-Spam-Status: No, score=-2.3 required=5.0 tests=AWL,BAYES_00,HTML_MESSAGE, SPF_PASS autolearn=ham version=3.1.1
Received: from [63.118.34.22] (helo=hicks.ciena.com) by psg.com with esmtp (Exim 4.60 (FreeBSD)) (envelope-from <Lyong@Ciena.com>) id 1G5VJA-0001Cr-8t for ccamp@ops.ietf.org; Tue, 25 Jul 2006 22:23:20 +0000
Received: from lin1-118-39-27.ciena.com (HELO mdmxm02.ciena.com) ([63.118.39.27]) by hicks.ciena.com with ESMTP; 25 Jul 2006 18:24:08 -0400
X-IronPort-AV: i="4.07,181,1151899200"; d="scan'208,217"; a="60260837:sNHT62292580"
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C6B038.CB1A8E6C"
Subject: RE: Proposed response to OIF on OSPF ENNI
Date: Tue, 25 Jul 2006 18:22:19 -0400
Message-ID: <0901D1988E815341A0103206A834DA07F1A2DB@mdmxm02.ciena.com>
In-Reply-To: <626FC7C6A97381468FB872072AB5DDC8C2DC28@XCH-SW-42.sw.nos.boeing.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: Proposed response to OIF on OSPF ENNI
Thread-Index: Acas0Ha/aYxFikOBS5m873SVRoVJxgAACLxQAAHPZJAAnZ89IAACGznwAAEH8mAAAxLNQAAAS4QQACJG/RAAAkvKMAANb1UQAABQfIAAASU6IAAAZZ6g
From: "Ong, Lyndon" <Lyong@Ciena.com>
To: "Drake, John E" <John.E.Drake2@boeing.com>, ccamp@ops.ietf.org
Sender: owner-ccamp@ops.ietf.org
Precedence: bulk
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 28dc73ba51024f450a593b05aa945739
I confess it was all rigged, John. Little midgets were inside the equipment plugging fibers here and there and typing RSVP messages into mini keypads. ________________________________ From: owner-ccamp@ops.ietf.org [mailto:owner-ccamp@ops.ietf.org] On Behalf Of Drake, John E Sent: Tuesday, July 25, 2006 3:08 PM To: ccamp@ops.ietf.org Subject: RE: Proposed response to OIF on OSPF ENNI -----Original Message----- From: Ong, Lyndon [mailto:Lyong@Ciena.com] Sent: Tuesday, July 25, 2006 2:39 PM To: Drake, John E; ccamp@ops.ietf.org Subject: RE: Proposed response to OIF on OSPF ENNI Hi John, If you wish to discuss how the tests were carried out, you can talk to the 7 major carriers that provided lab sites and the 13 router and switch vendors that participated in the 2005 demo. JD: Just as I suspected In what sense does IETF use the term interoperability test? JD: You know, the stuff required to advance to proposed standard Is there an RFC on this? JD: I'm sure. I was unaware that IETF ran interoperability tests. JD: I didn't say it did, and I don't know if it does. Cheers, Lyndon ________________________________ From: owner-ccamp@ops.ietf.org [mailto:owner-ccamp@ops.ietf.org] On Behalf Of Drake, John E Sent: Tuesday, July 25, 2006 2:28 PM To: ccamp@ops.ietf.org Subject: RE: Proposed response to OIF on OSPF ENNI Snipped Regarding Topic 2: Again I ask, wouldn't it be better to look at this document which has been implemented by many vendors, and successfully interoperability tested many times over many years to see what can be leveraged instead of starting from scratch? JD: I noticed that Jonathan has put in this plug several times. I am wondering whether these events are truly interoperability tests, in the sense that the IETF uses the term, or rather rigged demos? I seem to remember that the OIF characterized itself as a marketing organization. ________________________________
- Proposed response to OIF on OSPF ENNI Brungard, Deborah A, ALABS
- RE: Proposed response to OIF on OSPF ENNI Sadler, Jonathan B.
- RE: Proposed response to OIF on OSPF ENNI Ong, Lyndon
- RE: Proposed response to OIF on OSPF ENNI Brungard, Deborah A, ALABS
- RE: Proposed response to OIF on OSPF ENNI Ong, Lyndon
- RE: Proposed response to OIF on OSPF ENNI Sadler, Jonathan B.
- RE: Proposed response to OIF on OSPF ENNI Brungard, Deborah A, ALABS
- RE: Proposed response to OIF on OSPF ENNI Brungard, Deborah A, ALABS
- RE: Proposed response to OIF on OSPF ENNI Sadler, Jonathan B.
- RE: Proposed response to OIF on OSPF ENNI Sadler, Jonathan B.
- Re: Proposed response to OIF on OSPF ENNI Dimitri.Papadimitriou
- Re: Proposed response to OIF on OSPF ENNI Tomohiro Otani
- RE: Proposed response to OIF on OSPF ENNI Ong, Lyndon
- RE: Proposed response to OIF on OSPF ENNI Dimitri.Papadimitriou
- RE: Proposed response to OIF on OSPF ENNI Brungard, Deborah A, ALABS
- RE: Proposed response to OIF on OSPF ENNI Ong, Lyndon
- RE: Proposed response to OIF on OSPF ENNI Sadler, Jonathan B.
- RE: Proposed response to OIF on OSPF ENNI Ong, Lyndon
- RE: Proposed response to OIF on OSPF ENNI Dimitri.Papadimitriou
- RE: Proposed response to OIF on OSPF ENNI Dimitri.Papadimitriou
- RE: Proposed response to OIF on OSPF ENNI Ong, Lyndon
- RE: Proposed response to OIF on OSPF ENNI Dimitri.Papadimitriou
- RE: Proposed response to OIF on OSPF ENNI Dimitri.Papadimitriou
- RE: Proposed response to OIF on OSPF ENNI Brungard, Deborah A, ALABS
- RE: Proposed response to OIF on OSPF ENNI Sadler, Jonathan B.
- RE: Proposed response to OIF on OSPF ENNI Brungard, Deborah A, ALABS
- RE: Proposed response to OIF on OSPF ENNI Drake, John E
- RE: Proposed response to OIF on OSPF ENNI Ong, Lyndon
- Re: Proposed response to OIF on OSPF ENNI Richard Rabbat
- RE: Proposed response to OIF on OSPF ENNI Drake, John E
- RE: Proposed response to OIF on OSPF ENNI Ong, Lyndon
- RE: Proposed response to OIF on OSPF ENNI Drake, John E
- shared mesh restoration - e2e recovery signaling … Payam Torab
- RE: Proposed response to OIF on OSPF ENNI Ong, Lyndon
- Re: shared mesh restoration - e2e recovery signal… Dimitri.Papadimitriou
- RE: Proposed response to OIF on OSPF ENNI Dimitri.Papadimitriou
- RE: Proposed response to OIF on OSPF ENNI Drake, John E
- RE: Proposed response to OIF on OSPF ENNI Ong, Lyndon
- RE: Proposed response to OIF on OSPF ENNI Ong, Lyndon
- RE: shared mesh restoration - e2e recovery signal… Payam Torab
- RE: shared mesh restoration - e2e recovery signal… Dimitri.Papadimitriou
- RE: shared mesh restoration - e2e recovery signal… Payam Torab
- RE: shared mesh restoration - e2e recovery signal… Dimitri.Papadimitriou
- RE: Proposed response to OIF on OSPF ENNI Dimitri.Papadimitriou
- RE: Proposed response to OIF on OSPF ENNI MEURIC Julien RD-CORE-LAN
- Alignment of OIF routing requirements with CCAMP … Adrian Farrel
- Addressing draft [Was: Proposed response to OIF o… Adrian Farrel
- Re: Proposed response to OIF on OSPF ENNI Adrian Farrel
- RE: Proposed response to OIF on OSPF ENNI Ong, Lyndon
- RE: Proposed response to OIF on OSPF ENNI Drake, John E
- An IETF / OIF liaison relationship Was: (Re: Prop… Loa Andersson
- RE: Proposed response to OIF on OSPF ENNI Brungard, Deborah A, ALABS
- RE: Proposed response to OIF on OSPF ENNI Ong, Lyndon
- RE: Proposed response to OIF on OSPF ENNI Brungard, Deborah A, ALABS