IETF Logo Mail Archive

[netext] Comments on I-D: draft-sarikaya-netext-fb-support-extensions

<Basavaraj.Patil@nokia.com> Mon, 23 July 2012 17:11 UTC

Return-Path: <Basavaraj.Patil@nokia.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 A099D21F8596 for <netext@ietfa.amsl.com>; Mon, 23 Jul 2012 10:11:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.574
X-Spam-Level:
X-Spam-Status: No, score=-106.574 tagged_above=-999 required=5 tests=[AWL=0.025, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6cNFXSEk-oX5 for <netext@ietfa.amsl.com>; Mon, 23 Jul 2012 10:11:15 -0700 (PDT)
Received: from mgw-sa02.nokia.com (smtp.nokia.com [147.243.1.48]) by ietfa.amsl.com (Postfix) with ESMTP id 5F2CE21F859A for <netext@ietf.org>; Mon, 23 Jul 2012 10:11:15 -0700 (PDT)
Received: from vaebh101.NOE.Nokia.com (in-mx.nokia.com [10.160.244.22]) by mgw-sa02.nokia.com (Sentrion-MTA-4.2.2/Sentrion-MTA-4.2.2) with ESMTP id q6NHBDau029990 for <netext@ietf.org>; Mon, 23 Jul 2012 20:11:14 +0300
Received: from smtp.mgd.nokia.com ([65.54.30.24]) by vaebh101.NOE.Nokia.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675); Mon, 23 Jul 2012 20:11:51 +0300
Received: from 008-AM1MPN1-072.mgdnok.nokia.com ([169.254.2.83]) by 008-AM1MMR1-008.mgdnok.nokia.com ([65.54.30.24]) with mapi id 14.02.0283.004; Mon, 23 Jul 2012 19:11:13 +0200
From: Basavaraj.Patil@nokia.com
To: netext@ietf.org
Thread-Topic: Comments on I-D: draft-sarikaya-netext-fb-support-extensions
Thread-Index: AQHNaPYpTX/0CSvGiU6Gu/2cDgKw+g==
Date: Mon, 23 Jul 2012 17:11:12 +0000
Message-ID: <CC32EFE7.21A9C%basavaraj.patil@nokia.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.2.1.120420
x-originating-ip: [172.19.40.54]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <59C6AD8F5FE0CB4C8CC51B7E9F7BC031@mgd.nokia.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginalArrivalTime: 23 Jul 2012 17:11:51.0990 (UTC) FILETIME=[40AC7560:01CD68F6]
X-Nokia-AV: Clean
Subject: [netext] Comments on I-D: draft-sarikaya-netext-fb-support-extensions
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: Mon, 23 Jul 2012 17:11:21 -0000

A few comments:

1. I am not convinced with the problem statement specified in the I-D. The
WG flow-mobility I-D (draft-ietf-netext-pmipv6-flowmob) is intended to
provide a solution that is similar (albeit without UE interaction) to what
exists for MIP6. 

2. If the UE is assigned different HNPs to its interfaces as a result of
connecting via more than one interface, the current assumption is that
there is no switching of flows between those interfaces. The only case
where we enable flow mobility is when the UE has a single HNP assigned to
it but connected via multiple interfaces (possible via the use of
logical-interface at the UE).

3. The I-D does not explain how flow switching would work if the MN has
different HNPs assigned to its interfaces.The extensions to PMIP6
signaling with the new flags to support flow mobility can wait until you
have a clear explanation for the same.

-Raj

v2.30.2 | Report a Bug | By Email | System Status