Re: [netext] #16: requirement for single interface

<pierrick.seite@orange.com> Thu, 14 February 2013 11:41 UTC

Return-Path: <pierrick.seite@orange.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 D288F21F874C for <netext@ietfa.amsl.com>; Thu, 14 Feb 2013 03:41:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level:
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, UNPARSEABLE_RELAY=0.001]
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 UXSyPCYIArF0 for <netext@ietfa.amsl.com>; Thu, 14 Feb 2013 03:41:24 -0800 (PST)
Received: from relais-inet.francetelecom.com (relais-ias92.francetelecom.com [193.251.215.92]) by ietfa.amsl.com (Postfix) with ESMTP id D93BC21F874A for <netext@ietf.org>; Thu, 14 Feb 2013 03:41:23 -0800 (PST)
Received: from omfedm05.si.francetelecom.fr (unknown [xx.xx.xx.1]) by omfedm10.si.francetelecom.fr (ESMTP service) with ESMTP id 2CCC5264767; Thu, 14 Feb 2013 12:41:23 +0100 (CET)
Received: from Exchangemail-eme1.itn.ftgroup (unknown [10.114.1.186]) by omfedm05.si.francetelecom.fr (ESMTP service) with ESMTP id 0679035C064; Thu, 14 Feb 2013 12:41:23 +0100 (CET)
Received: from PEXCVZYM12.corporate.adroot.infra.ftgroup ([fe80::81f:1640:4749:5d13]) by PEXCVZYH01.corporate.adroot.infra.ftgroup ([::1]) with mapi id 14.02.0318.004; Thu, 14 Feb 2013 12:41:22 +0100
From: <pierrick.seite@orange.com>
To: 'netext issue tracker' <trac+netext@trac.tools.ietf.org>, "draft-ietf-netext-pmipv6-flowmob@tools.ietf.org" <draft-ietf-netext-pmipv6-flowmob@tools.ietf.org>, "cjbc@it.uc3m.es" <cjbc@it.uc3m.es>
Thread-Topic: [netext] #16: requirement for single interface
Thread-Index: AQHOChj69s2NLES+PUCmzWM28Y0H75h5NY7Q
Date: Thu, 14 Feb 2013 11:41:21 +0000
Message-ID: <11267_1360842083_511CCD63_11267_3596_1_81C77F07008CA24F9783A98CFD706F7108D146@PEXCVZYM12.corporate.adroot.infra.ftgroup>
References: <066.3e6b8aecad5b672bd54c5b2b61eaa5bd@trac.tools.ietf.org> <081.6bc5077dba4b0f70b8827703427f353d@trac.tools.ietf.org>
In-Reply-To: <081.6bc5077dba4b0f70b8827703427f353d@trac.tools.ietf.org>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.197.38.1]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-PMX-Version: 5.6.1.2065439, Antispam-Engine: 2.7.2.376379, Antispam-Data: 2013.2.14.100316
Cc: "netext@ietf.org" <netext@ietf.org>
Subject: Re: [netext] #16: requirement for single interface
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: Thu, 14 Feb 2013 11:41:25 -0000

> -----Message d'origine-----
> De : netext-bounces@ietf.org [mailto:netext-bounces@ietf.org] De la
> part de netext issue tracker
> Envoyé : mercredi 13 février 2013 19:36
> À : draft-ietf-netext-pmipv6-flowmob@tools.ietf.org; cjbc@it.uc3m.es
> Cc : netext@ietf.org
> Objet : Re: [netext] #16: requirement for single interface
> 
> #16: requirement for single interface
> 
> 
> Comment (by cjbc@it.uc3m.es):
> 
>  This was introduced to address the review performed by Marco Liebsch,
> and  also the suggestions from the chairs, to remove a strong
> dependency on the  logical interface.
> 
>  If two different IP addresses are configured, IP session continuity is
> still possible (for each of the configured IP addresses). What is
> needed  is the network to deliver packets for IP X to the right MN's
> physical  interface, and the MN to select the right outgoing interface
> when sending  traffic back (of course using IP X as source address).
> 

Ok. I guess that, in this case, mobility of an IP flow requests the MN to support the weak host model, right? 

May I suggest to reword the following sentence (section 3.2.1)

[if the IP layer at the mobile node shows one single interface, then the mobile node has one single IPv6 address configured at the IP layer: pref1::mn1. Otherwise, two different IPv6 addresses (pref1::if1 and pref1::if2) would be configured.]

As

[if the IP layer at the mobile node shows one single logical interface [ref to logical interface I-D], then the mobile node has one single IPv6 address configured at the IP layer: pref1::mn1. Otherwise, per interface IPv6 addresses (e.g. pref1::if1 and pref1::if2) would be configured; each address must be valid on every interfaces.]

> --
> -------------------------------------+---------------------------------
> -
> -------------------------------------+---
>  Reporter:                           |       Owner:  draft-ietf-netext-
>   pierrick.seite@orange.com          |  pmipv6-flowmob@tools.ietf.org
>      Type:  defect                   |      Status:  new
>  Priority:  major                    |   Milestone:
> Component:  pmipv6-flowmob           |     Version:
>  Severity:  Active WG Document       |  Resolution:
>  Keywords:                           |
> -------------------------------------+---------------------------------
> -
> -------------------------------------+---
> 
> Ticket URL:
> <https://trac.tools.ietf.org/wg/netext/trac/ticket/16#comment:1>
> netext <http://tools.ietf.org/netext/>
> 
> _______________________________________________
> netext mailing list
> netext@ietf.org
> https://www.ietf.org/mailman/listinfo/netext

_________________________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
France Telecom - Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, France Telecom - Orange is not liable for messages that have been modified, changed or falsified.
Thank you.