RE: individual submission Last Call -- default yes/no.

John C Klensin <john-ietf@jck.com> Tue, 11 January 2005 01:20 UTC

Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA20884; Mon, 10 Jan 2005 20:20:15 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CoAvT-0007zf-Pt; Mon, 10 Jan 2005 20:34:28 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CoAZY-0007Sq-De; Mon, 10 Jan 2005 20:11:48 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CoAWP-00077u-SN for ietf@megatron.ietf.org; Mon, 10 Jan 2005 20:08:34 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA20150 for <ietf@ietf.org>; Mon, 10 Jan 2005 20:08:30 -0500 (EST)
Received: from ns.jck.com ([209.187.148.211] helo=bs.jck.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CoAk7-0007n2-W6 for ietf@ietf.org; Mon, 10 Jan 2005 20:22:44 -0500
Received: from [209.187.148.215] (helo=scan.jck.com) by bs.jck.com with esmtp (Exim 4.34) id 1CoAWK-0006Cq-8g; Mon, 10 Jan 2005 20:08:28 -0500
Date: Mon, 10 Jan 2005 20:08:28 -0500
From: John C Klensin <john-ietf@jck.com>
To: Misha Wolf <Misha.Wolf@reuters.com>
Message-ID: <004123E5941A87F5D960793D@scan.jck.com>
In-Reply-To: <1987416CA83AC7499AC772F92E2DBF7802CCD3B7@LONSMSXM02.emea.ime.reuters.com>
References: <1987416CA83AC7499AC772F92E2DBF7802CCD3B7@LONSMSXM02. emea.ime.reuters.com>
X-Mailer: Mulberry/3.1.6 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f60d0f7806b0c40781eee6b9cd0b2135
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
Subject: RE: individual submission Last Call -- default yes/no.
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: fb6060cb60c0cea16e3f7219e40a0a81
Content-Transfer-Encoding: 7bit


--On Monday, 10 January, 2005 21:29 +0000 Misha Wolf
<Misha.Wolf@reuters.com> wrote:

> Vernon Schryver wrote:
> 
> vs> unless the incredible "I'm gona tell the Liason on you" 
> vs> threat was the vacuous, standards committee politicing 
> vs> as usual that it sounded like.
> 
> That appears to be a rather paranoid reading of my:
> 
> mw> Now the IETF is, of course, free to do whatever it likes, 
> mw> but I would urge that any course of action which would 
> mw> cause a parting of the ways between the IETF and the W3C 
> mw> (and other Industry Consortia) should be avoided.  I 
> mw> suggest that it may be time to escalate this matter to 
> mw> the IETF/W3C Liaison group.
> 
> Where is the threat?  I was suggesting that as the IETF and 
> the W3C have a liaison group and as there appear to be 
> disagreements as to how to move forward, the matter be raised 
> at the liaison group.  Is that not what such groups are for?

Misha,

Ignoring, for the moment, several other aspects of your
statement that I, and apparently some others, found upsetting,
liaison or groups like that one are usually constituted to sort
out issues arising between real or official projects of the
relevant groups.  In some cases, they can be, and have been,
used very effectively to sort out issues arising between the
projects or work program of one group and somewhat-related work
program items of the other group.  But, in this case, 

	* We have been assured that there is no W3C project in
	this area.
	
	* There is also no IETF project in this area: we have no
	mechanisms for having projects outside of the WG process
	and activities for which the IAB or IRTF formally sign
	up (and it is always an open question whether the latter
	two are "IETF projects" or not).
	
	* And, regardless of the fact that some people are doing
	work in both places, there is no formal liaison between
	the IETF and W3C over language tag issues (and the IETF
	has never recognized "informal liaisons" as having any
	standing).

So, while I'm much in favor of the ability of that particular
coordination group to discuss whatever its members find
interesting, I can't imagine what you think a discussion there
would accomplish in this case.  It has no ability to create IETF
WGs, even though several of its members are IESG members who
might participate in a WG creating process.   Not even the IESG
has the ability to retroactively turn a design team-like
discussion into a WG.  Similarly that group has no authority to
turn this effort into a W3C project with which the IETF would
feel an obligation to coordinate.  And certainly it can't create
a joint standards development activity or overrule the IESG on a
decision about consensus in the _IETF_ community.

So I'm having trouble seeing that suggestion as helpful.

     john


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