Re: [rrg] Recommendation and what happens next

Tony Li <tony.li@tony.li> Mon, 08 March 2010 04:50 UTC

Return-Path: <tony.li@tony.li>
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 98A803A68E0 for <rrg@core3.amsl.com>; Sun, 7 Mar 2010 20:50:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.174
X-Spam-Level:
X-Spam-Status: No, score=-2.174 tagged_above=-999 required=5 tests=[AWL=0.425, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Y-Mt45HYhiZL for <rrg@core3.amsl.com>; Sun, 7 Mar 2010 20:50:47 -0800 (PST)
Received: from qmta07.emeryville.ca.mail.comcast.net (qmta07.emeryville.ca.mail.comcast.net [76.96.30.64]) by core3.amsl.com (Postfix) with ESMTP id 314093A68DD for <rrg@irtf.org>; Sun, 7 Mar 2010 20:50:47 -0800 (PST)
Received: from omta07.emeryville.ca.mail.comcast.net ([76.96.30.59]) by qmta07.emeryville.ca.mail.comcast.net with comcast id qUKj1d0061GXsucA7Uqsir; Mon, 08 Mar 2010 04:50:52 +0000
Received: from [10.21.115.24] ([128.107.239.233]) by omta07.emeryville.ca.mail.comcast.net with comcast id qUqc1d00352qHCY8TUqfNb; Mon, 08 Mar 2010 04:50:49 +0000
User-Agent: Microsoft-Entourage/12.23.0.091001
Date: Sun, 07 Mar 2010 20:50:34 -0800
From: Tony Li <tony.li@tony.li>
To: Robin Whittle <rw@firstpr.com.au>, RRG <rrg@irtf.org>
Message-ID: <C7B9C21A.4FAB%tony.li@tony.li>
Thread-Topic: [rrg] Recommendation and what happens next
Thread-Index: Acq+euMqy73fYEOnLUGuyMDVvQvsYA==
In-Reply-To: <4B94617E.1010104@firstpr.com.au>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
Cc: Lixia Zhang <lixia@CS.UCLA.EDU>
Subject: Re: [rrg] Recommendation and what happens next
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Mar 2010 04:50:48 -0000

Hi Robin,

> OK - but where have you encouraged debate, or contributed to it by
> arguing for your own preferred position?

Well Robin, I have to admit, I've been far less prolific than you have been.
However, for the last three years, I've been plugging away for an
enlightened debate about the solution space.  No takers.  I've argued for my
position in the past and been slammed with ~"that can't possibly work"~

> I understand you support
> ILNP (CEE, Locator / Identity Separation) - which are only practical
> for IPv6.  I am not sure what you want for IPv4.

I want nothing.  IPv4 is done.  Over.  Cooked. Fully toast.  It will either
enter a black market where we deaggregate and no proposal will help, or we
shift to v6 and v4 is irrelevant.  In either case, we're not in time to do
anything significant for v4.  And we still need a v6 solution, that's
clearly higher priority.

>>>> What I expect will happen will look like:
>>>> 
>>>>     - Some initial discussion
>>>>     - Presentation of the recommendation
>>>>     - Feedback afterwards
>>> 
>>> OK - I understand from this you have no clear idea of what will happen.
>> 
>> That's as clear as I can make it.  What were you hoping for?
> 
> Since you are one of the co-chairs and you are urging us - indeed
> expecting us - by so-far unspecified methods, to develop and in some
> way be happy with a single-architecture Recommendation in the next 19
> days, I was hoping you would be able to give us more guidance about
> how to debate this, including leading by example: by arguing in
> detail for your own preferred outcomes.  Lixia has done this for her
> AIS (Evolution) proposal.

I'm not expecting anyone to develop a recommendation.  I'm not expecting
anyone to be happy with it.

> You haven't yet stated when you and Lixia intend to finalise the text
> of the RRG Report, at which point you will choose what, if anything,
> goes in the Recommendation section.  Nor have you explained how you
> will choose the text, or guide the mailing list or meeting discussions.

We will present the results at our next meeting.  After that, we will polish
the text and then publish the final document.  We will certainly be happy to
take input on the text, but we will not promise to incorporate any of it.

> Do you intend to finalise the Recommendation during the meeting, or
> afterwards?  If the former, than I am concerned that those not at the
> meeting will be at a disadvantage through not being able to be
> express our arguments as directly as those who can attend.  If the
> latter, do you have any plans for how long after the meeting you will
> finalise the text?

Again, finalizing the text will be later.  Yes, regardless, you're at a
disadvantage being remote.  Sorry, but the IRTF (unlike the IETF) has no
constraints about the mailing list being the primary mode of operation.  Nor
are there requirements for us to do anything to support remote
participation.  We do try to, but that's mostly thanks to co-location with
IETF.

> This is a statement about the past.  If this continues for the next
> few weeks, then there will be no large enough subset of active RRG
> participants with a compatible opinion to form anything like
> consensus.  But I doubt that everyone would hold to their own
> proposals in the context of a detailed, constructive, debate - a
> debate we are yet to have.

Again, we've been trying to have that debate for three years.

> OK - but if you and Lixia include text as a "Recommendation" without
> a process which tests support for it - or if there is such a test and
> it only gets minority support - then the "Recommendation" won't have
> much value or be taken particularly seriously by the IESG or anyone else.

Again, the IRTF is not bound by a consensus process.  In the preceding years
where we've tried to drive consensus, we've gotten no response.  We're left
making a call without consensus.  If that means that it doesn't have broad
support, well, so be it.  We committed to a deliverable and we're going to
see it through.

> I don't recall you or Lixia write anything about what various groups
> of people have in common and where they differ.

That's because we would never reach consensus on what _that_ text would be
either.

> Sure - but if that is the best we can do, then surely it would be
> better to produce a coherent report on the various positions which
> people have adopted, with the arguments each group advances in
> support of their position, and the arguments they provide against the
> positions of others.

Done.

> To pretend that the situation involved more agreement than it really
> does would be a worse failure.

No one is claiming agreement.

Tony