Vendor standardization (was: IETF chair's blog)

SM <sm@resistor.net> Mon, 25 February 2013 16:39 UTC

Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EB0B421F95D9 for <ietf@ietfa.amsl.com>; Mon, 25 Feb 2013 08:39:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.576
X-Spam-Level:
X-Spam-Status: No, score=-102.576 tagged_above=-999 required=5 tests=[AWL=0.023, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FBgwoZE1e3sz for <ietf@ietfa.amsl.com>; Mon, 25 Feb 2013 08:39:10 -0800 (PST)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 7F48121F95D8 for <ietf@ietf.org>; Mon, 25 Feb 2013 08:39:10 -0800 (PST)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r1PGd0da026917; Mon, 25 Feb 2013 08:39:03 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1361810345; bh=v7SKqoSUJJpLQVAkdw8y/HX+5e1Hd1PQCHwDFv8PGfo=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=NudzuQ0zxQjUzuPN2bl9CsZfvn/ulpsSARvALSuAUaYHOZKPiftTmCB5rhX+/a2E+ gyAZeTavRIMJAdIVhYQRm3rWztHJOletIbqWk5F0q89usaI5otMsctCx4j1uzNJOr9 wpv8xpMGDAvH/fZ/HgeL6cPhRar1CzHKNsmook6E=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1361810345; i=@resistor.net; bh=v7SKqoSUJJpLQVAkdw8y/HX+5e1Hd1PQCHwDFv8PGfo=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=MxNI+zqbO0iXMHqStsRZRZ+poyR8hcrJyPOpBNaZcN6345fQNjbAB09XpJqVEKQr/ mJ7vkerMunMBY1M5hcW+87oBa5nQZE18h31TEPhKafj2uQ2pjEvqRSpgZWvbcO9DRK NtlfIAbbRKcDwShZXzIw1eg6+kqcrrNUuoa4hk8A=
Message-Id: <6.2.5.6.2.20130225072932.09f0be18@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Mon, 25 Feb 2013 08:37:28 -0800
To: Simon Pietro Romano <spromano@unina.it>
From: SM <sm@resistor.net>
Subject: Vendor standardization (was: IETF chair's blog)
In-Reply-To: <BBB5AA20-D2EF-4F90-BF98-993A1AFE25DB@unina.it>
References: <1BBAE003-DEA4-462A-998D-863F6FF90A69@ietf.org> <51298B1E.60007@lacnic.net> <512A5A10.4090406@acm.org> <8C48B86A895913448548E6D15DA7553B7A52DA@xmb-rcd-x09.cisco.com> <512B1EBA.30507@gmail.com> <BBB5AA20-D2EF-4F90-BF98-993A1AFE25DB@unina.it>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 25 Feb 2013 16:39:13 -0000

Hi Simon,
At 03:15 25-02-2013, Simon Pietro Romano wrote:
>Just out of curiosity, can you list which of the above requirements 
>is not met by Meetecho?

Meetecho is a vendor.  In my humble opinion the IETF "standardizes" 
on protocols; it does not "standardize" on vendors.  I can still 
access the audio for IETF 56 which are hosted on IETF 
infrastructure.  I may not be able to access the links [1] provided 
by Meetecho [2] in future.

 From the Universi Dominici Gregis:

   "While keeping in mind present-day requirements, I have been careful, in
    formulating the new discipline, not to depart in substance from the wise
    and venerable tradition already established."

Regards,
-sm

1. http://www.ietf.org/mail-archive/web/video-codec/current/msg00068.html
2. It applies to WebEx too.