Re: [netext] Comment on draft-gundavelli-netext-pmipv6-sipto-option-01

Sri Gundavelli <sgundave@cisco.com> Tue, 26 July 2011 04:30 UTC

Return-Path: <sgundave@cisco.com>
X-Original-To: netext@ietfa.amsl.com
Delivered-To: netext@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D10AD11E80FD for <netext@ietfa.amsl.com>; Mon, 25 Jul 2011 21:30:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.34
X-Spam-Level:
X-Spam-Status: No, score=-3.34 tagged_above=-999 required=5 tests=[AWL=-0.741, BAYES_00=-2.599]
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 VKOFP-hni9EQ for <netext@ietfa.amsl.com>; Mon, 25 Jul 2011 21:30:29 -0700 (PDT)
Received: from rcdn-iport-1.cisco.com (rcdn-iport-1.cisco.com [173.37.86.72]) by ietfa.amsl.com (Postfix) with ESMTP id 2E3A011E807F for <netext@ietf.org>; Mon, 25 Jul 2011 21:30:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=sgundave@cisco.com; l=961; q=dns/txt; s=iport; t=1311654629; x=1312864229; h=date:subject:from:to:cc:message-id:in-reply-to: mime-version:content-transfer-encoding; bh=vuNdq5CAwDmABr+hGjiJ+48Zp1E7+Z22sceWyrMFxqs=; b=hfPqaY2wxZfl6qAZ69G3gPqcszP63KzaHJJR584pJcgdFagSGEPJyONI aa2UjZkDqcoCGSvXA4DQlRYActdqAJ7JKrhC/TJAfRK5BOD8iueLeap/F 2twOwOZN2r0h5EjJQ20vU1squsDQhI+IpMwa9TAziDYMz4zh9whRu68pj c=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av4EAHZCLk6rRDoI/2dsb2JhbAA0AQEBAQIBFAErAwFBBQ4BCWZRAQEFDwgnpzR3iHyiVZ5ehj8Eh1eLG4UQi3A
X-IronPort-AV: E=Sophos;i="4.67,266,1309737600"; d="scan'208";a="6353171"
Received: from mtv-core-3.cisco.com ([171.68.58.8]) by rcdn-iport-1.cisco.com with ESMTP; 26 Jul 2011 04:30:28 +0000
Received: from xbh-sjc-231.amer.cisco.com (xbh-sjc-231.cisco.com [128.107.191.100]) by mtv-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id p6Q4USnF032605; Tue, 26 Jul 2011 04:30:28 GMT
Received: from xmb-sjc-214.amer.cisco.com ([171.70.151.145]) by xbh-sjc-231.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.4675); Mon, 25 Jul 2011 21:30:27 -0700
Received: from 10.32.243.37 ([10.32.243.37]) by xmb-sjc-214.amer.cisco.com ([171.70.151.145]) with Microsoft Exchange Server HTTP-DAV ; Tue, 26 Jul 2011 04:30:27 +0000
User-Agent: Microsoft-Entourage/12.30.0.110427
Date: Mon, 25 Jul 2011 21:30:26 -0700
From: Sri Gundavelli <sgundave@cisco.com>
To: Hidetoshi Yokota <yokota@kddilabs.jp>
Message-ID: <CA5390F2.226DA%sgundave@cisco.com>
Thread-Topic: [netext] Comment on draft-gundavelli-netext-pmipv6-sipto-option-01
Thread-Index: AcxLTL3APNC3LHVQOUaP6W+Epipivw==
In-Reply-To: <4E2E1655.4070908@kddilabs.jp>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
X-OriginalArrivalTime: 26 Jul 2011 04:30:27.0982 (UTC) FILETIME=[BEEECAE0:01CC4B4C]
Cc: "netext@ietf.org" <netext@ietf.org>
Subject: Re: [netext] Comment on draft-gundavelli-netext-pmipv6-sipto-option-01
X-BeenThere: netext@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Mailing list for discusion of extensions to network mobility protocol, i.e PMIP6. " <netext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netext>, <mailto:netext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/netext>
List-Post: <mailto:netext@ietf.org>
List-Help: <mailto:netext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netext>, <mailto:netext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 26 Jul 2011 04:30:29 -0000

Hi Yokota-san,

Thanks. More than the option, the specification scope and use-case is
different. We don't need to add SIPTO to flow mobility scope, already that
draft is struggling to make any progress with the amount of features it has
and finding convergence among authors/WG. We don't have to add this to the
mix :) and make it more interesting. Hopefully, that draft will cut some
features and make some progress.


Again, thanks for your review and support for the work.

Regards
Sri




On 7/25/11 6:20 PM, "Hidetoshi Yokota" <yokota@kddilabs.jp> wrote:

> Hi Sri,
> 
> Thanks for your clarification. SIPTO capability extension for PMIP is as
> much important. I just thought if these two capabilities (flow mobility
> and offload) could be combined as a protocol. Either to use the option
> in your draft or to define a new flag in PMIP flow mobility draft. I
> would like to see the discussion in the meeting.
> 
> Regards,