IETF Logo Mail Archive

Re: [rrg] Recommendation and what happens next

Scott Brim <scott.brim@gmail.com> Thu, 11 March 2010 22:36 UTC

Return-Path: <scott.brim@gmail.com>
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 D1D2A3A696C for <rrg@core3.amsl.com>; Thu, 11 Mar 2010 14:36:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.742
X-Spam-Level:
X-Spam-Status: No, score=-2.742 tagged_above=-999 required=5 tests=[AWL=-0.143, 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 ZbCKJrcpwZaA for <rrg@core3.amsl.com>; Thu, 11 Mar 2010 14:36:46 -0800 (PST)
Received: from mail-qy0-f185.google.com (mail-qy0-f185.google.com [209.85.221.185]) by core3.amsl.com (Postfix) with ESMTP id 25DCD3A6984 for <rrg@irtf.org>; Thu, 11 Mar 2010 14:36:41 -0800 (PST)
Received: by qyk15 with SMTP id 15so592749qyk.10 for <rrg@irtf.org>; Thu, 11 Mar 2010 14:36:45 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :x-enigmail-version:content-type:content-transfer-encoding; bh=jhhXVOsEO6fV37xCvDUH5l0s3ia6OFR/reSwNEbwupM=; b=Fthj7+D64CsU0e6+DEwoMPiD5lv11cFnWJPIK5qtqlik+J8c8v97Pn+OMNWjpXCDjs aJ7y+DdEyyEDT2Ty9qL6Z8X7Ic04m9v9jC5JaVIOUeB0qNvKlmnC191T2OLbRXeFUjeC zwzsY8Ui7j76de5uLmhoGmVcbQDB5aBBo6SeM=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:x-enigmail-version:content-type :content-transfer-encoding; b=Oath9PnBzXWWey6N1G2Q/A4iVW2m0KUuaJUUWSHTyo3cTBZ38QU+BdwHiR7BJ5CHhD OKVXmM8UtsTx93A9fXupnjdJbkbtDHGZ8TQxF/O0Y6nHSqWesweEro0oi3builQCc3bB F6CygwxUvQA+f1fQfNTZH1lkPHebL84uoXrlc=
Received: by 10.229.233.75 with SMTP id jx11mr103265qcb.84.1268347004931; Thu, 11 Mar 2010 14:36:44 -0800 (PST)
Received: from bxb-vpn3-621.cisco.com (198-135-0-233.cisco.com [198.135.0.233]) by mx.google.com with ESMTPS id 4sm1229891qwe.6.2010.03.11.14.36.42 (version=TLSv1/SSLv3 cipher=RC4-MD5); Thu, 11 Mar 2010 14:36:43 -0800 (PST)
Message-ID: <4B997078.6000906@gmail.com>
Date: Thu, 11 Mar 2010 17:36:40 -0500
From: Scott Brim <scott.brim@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.1.8) Gecko/20100227 Lightning/1.0b1 Thunderbird/3.0.3
MIME-Version: 1.0
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>
References: <C7B951B7.4F5D%tony.li@tony.li> <4B945997.9080704@cisco.com> <4B969703.3040901@gmail.com> <E1829B60731D1740BB7A0626B4FAF0A64951193A22@XCH-NW-01V.nw.nos.boeing.com> <4B97CC82.70808@gmail.com> <E1829B60731D1740BB7A0626B4FAF0A6495119415F@XCH-NW-01V.nw.nos.boeing.com>
In-Reply-To: <E1829B60731D1740BB7A0626B4FAF0A6495119415F@XCH-NW-01V.nw.nos.boeing.com>
X-Enigmail-Version: 1.0.1
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Cc: RRG <rrg@irtf.org>, Russ White <russ@cisco.com>
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: Thu, 11 Mar 2010 22:36:46 -0000

Templin, Fred L allegedly wrote on 03/11/2010 17:18 EST:
>> Suppose the generic question everyone should answer is "how does the
>> proposed system constrain or promote specific approaches to endpoint and
>> network mobility?".
> 
> That is a very good question.

I guess RRG will not get around to asking about how each proposal
impacts mobility, but when the IETF does, this should be answered for
each proposal.

v2.23.0 | Report a Bug | By Email