Re: [mif] Follow up with BBF proposal

"Sri Gundavelli (sgundave)" <sgundave@cisco.com> Tue, 11 November 2014 01:08 UTC

Return-Path: <sgundave@cisco.com>
X-Original-To: mif@ietfa.amsl.com
Delivered-To: mif@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E96341A1BC8 for <mif@ietfa.amsl.com>; Mon, 10 Nov 2014 17:08:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.094
X-Spam-Level:
X-Spam-Status: No, score=-15.094 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.594, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HwL7lQqpIjTO for <mif@ietfa.amsl.com>; Mon, 10 Nov 2014 17:08:43 -0800 (PST)
Received: from alln-iport-1.cisco.com (alln-iport-1.cisco.com [173.37.142.88]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5F4F01A1AAD for <mif@ietf.org>; Mon, 10 Nov 2014 17:08:43 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=12882; q=dns/txt; s=iport; t=1415668124; x=1416877724; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=CnHmBV8k95mJkKBZZdVIP2Ts1bENcgBvzRlah231vy8=; b=ZOhw3/WGrsgd8EmclIj1mHmJCJHiKn0b3Hd2TfyaVvvVdc1u7TkPQu4q ItZGSRN1jvIrDSyAaunhsbntsBbPlPrGu6n1F8qhZeXEX0OEgSjZ4mkbg yOdjroulCsywackLoIzpZi6oJndOVutNf8Auk4vQSwM7DKmEVuzoX+QKr c=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AlEFAGJgYVStJV2b/2dsb2JhbABcgkhGVFkEu1qOOIFuh08CgR8WAQEBAQF9hAIBAQEELUwQAgEIEQMBAigHIREUCQgCBAENBRuIEQMSDcYxDYZTAQEBAQEBAQEBAQEBAQEBAQEBAQEBF45cghUTEQYBhEsFkjGEU4UPghKBcY1+hnGDemyBSIEDAQEB
X-IronPort-AV: E=Sophos; i="5.07,356,1413244800"; d="scan'208,217"; a="95288408"
Received: from rcdn-core-4.cisco.com ([173.37.93.155]) by alln-iport-1.cisco.com with ESMTP; 11 Nov 2014 01:08:43 +0000
Received: from xhc-aln-x02.cisco.com (xhc-aln-x02.cisco.com [173.36.12.76]) by rcdn-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id sAB18g94018516 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 11 Nov 2014 01:08:42 GMT
Received: from xmb-aln-x03.cisco.com ([169.254.6.32]) by xhc-aln-x02.cisco.com ([173.36.12.76]) with mapi id 14.03.0195.001; Mon, 10 Nov 2014 19:08:42 -0600
From: "Sri Gundavelli (sgundave)" <sgundave@cisco.com>
To: "'STARK, BARBARA H'" <bs7652@att.com>, Hui Deng <denghui@chinamobile.com>
Thread-Topic: Follow up with BBF proposal
Thread-Index: AQHP/UwID8Bhv/YxaE+5ucazw5UALQ==
Date: Tue, 11 Nov 2014 01:08:41 +0000
Message-ID: <D0869CBD.177FDF%sgundave@cisco.com>
References: <01FE63842C181246BBE4CF183BD159B449037ECA@nkgeml504-mbx.china.huawei.com> <D0765101.175805%sgundave@cisco.com> <005401cff509$3719eb30$a54dc190$@com>
In-Reply-To: <005401cff509$3719eb30$a54dc190$@com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.4.5.141003
x-originating-ip: [10.21.69.71]
Content-Type: multipart/alternative; boundary="_000_D0869CBD177FDFsgundaveciscocom_"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/mif/jKO4Beii3NED5idt1R7TLwxxLO8
Cc: Brian Haberman <brian@innovationslab.net>, "mif@ietf.org" <mif@ietf.org>
Subject: Re: [mif] Follow up with BBF proposal
X-BeenThere: mif@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multiple Interface Discussion List <mif.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mif>, <mailto:mif-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mif/>
List-Post: <mailto:mif@ietf.org>
List-Help: <mailto:mif-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mif>, <mailto:mif-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 11 Nov 2014 01:08:46 -0000

Hi Hui,

The BBF requirement as presented in the BBF documents and as interpreted in draft-seite and draft-lhwxz is about enabling a CPE device to attach to multiple access network and perform flow management. However, I look at it, I see this this is a mobility requirement and is really not in the scope of MIF WG. The BBF requirement in question is all about flow switching or flow splitting across access systems. I'm not sure why this work belongs MIF and not DMM which is chartered to handle all mobility use-cases. We have discussed this specific use-case of flow splitting during MIF formation and explicitly disallowed MIF WG from taking up such work. The following is the quote from the MIF chartered text. Also, the MIF WG was primarily looking at issues for a host attached to multiple access networks, but the hybrid access is about a CPE attached to multiple networks. I really think this work should be done in DMM and we did present the requirements in the last IETF meeting.


http://datatracker.ietf.org/wg/mif/charter/

No work will be done to enable traffic flows to move from one interface to another. The group recognizes existing work on mechanisms that require peer or network support for moving traffic flows such as RFC 5206, RFC 4980 and the use of multiple care-of addresses in Mobile IPv6. This group does not work on or impact such mechanisms. Future work in this area requires rechartering the working group or asking other, specialized working groups (such as DHC or 6MAN) to deal with specific issues.




Regards
Sri

From: Hui Deng <denghui@chinamobile.com<mailto:denghui@chinamobile.com>>
Date: Friday, October 31, 2014 4:50 AM
To: Sri Gundavelli <sgundave@cisco.com<mailto:sgundave@cisco.com>>, 'Xueli' <xueli@huawei.com<mailto:xueli@huawei.com>>, "pierrick.seite@orange.com<mailto:pierrick.seite@orange.com>" <pierrick.seite@orange.com<mailto:pierrick.seite@orange.com>>, 'Ted Lemon' <Ted.Lemon@nominum.com<mailto:Ted.Lemon@nominum.com>>, "'STARK, BARBARA H'" <bs7652@att.com<mailto:bs7652@att.com>>, 'Alexandru Petrescu' <alexandru.petrescu@gmail.com<mailto:alexandru.petrescu@gmail.com>>
Cc: "mif@ietf.org<mailto:mif@ietf.org>" <mif@ietf.org<mailto:mif@ietf.org>>
Subject: Follow up with BBF proposal

Hi everybody

I am recommending that Xue Li could help to put down the slide for the problem statement from BBF.

And MIP/NEMO proponents (Pierrick, Alex, Sri) and Xue Li could kindly to meet together during IETF meeting
to discuss by adding s thelide about how today solutions meet the requirement or there are some gap still, and whether that problem should be solvable in IETF.

Chairs will talk with AD whether MIF or somewhere else will consider to discuss those issues during the f2f session.

Best regards,

-Hui