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

Carlos Jesús Bernardos Cano <cjbc@it.uc3m.es> Thu, 14 February 2013 21:22 UTC

Return-Path: <cjbc@it.uc3m.es>
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 B839B21F85BB for <netext@ietfa.amsl.com>; Thu, 14 Feb 2013 13:22:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.299
X-Spam-Level:
X-Spam-Status: No, score=-6.299 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
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 KnGS5lhN26vl for <netext@ietfa.amsl.com>; Thu, 14 Feb 2013 13:22:44 -0800 (PST)
Received: from smtp03.uc3m.es (smtp03.uc3m.es [163.117.176.133]) by ietfa.amsl.com (Postfix) with ESMTP id C9DE421F873B for <netext@ietf.org>; Thu, 14 Feb 2013 13:22:43 -0800 (PST)
Received: from smtp03.uc3m.es (localhost [127.0.0.1]) by localhost.uc3m.es (Postfix) with ESMTP id 44E301162D3A; Thu, 14 Feb 2013 22:22:42 +0100 (CET)
X-uc3m-safe: yes
X-uc3m-safe: yes
Received: from [192.168.1.3] (82.158.126.26.dyn.user.ono.com [82.158.126.26]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: cjbc@smtp03.uc3m.es) by smtp03.uc3m.es (Postfix) with ESMTPSA id E18DB118505D; Thu, 14 Feb 2013 22:22:40 +0100 (CET)
Message-ID: <1360876960.4271.33.camel@acorde.it.uc3m.es>
From: Carlos =?ISO-8859-1?Q?Jes=FAs?= Bernardos Cano <cjbc@it.uc3m.es>
To: pierrick.seite@orange.com
Date: Thu, 14 Feb 2013 22:22:40 +0100
In-Reply-To: <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> <11267_1360842083_511CCD63_11267_3596_1_81C77F07008CA24F9783A98CFD706F7108D146@PEXCVZYM12.corporate.adroot.infra.ftgroup>
Organization: Universidad Carlos III de Madrid
Content-Type: text/plain; charset="UTF-8"
X-Mailer: Evolution 3.4.4-1
Mime-Version: 1.0
Content-Transfer-Encoding: 8bit
X-TM-AS-Product-Ver: IMSS-7.1.0.1224-7.0.0.1014-19638.002
X-TM-AS-Result: No--22.401-7.0-31-1
X-imss-scan-details: No--22.401-7.0-31-1
Cc: 'netext issue tracker' <trac+netext@trac.tools.ietf.org>, "netext@ietf.org" <netext@ietf.org>, "draft-ietf-netext-pmipv6-flowmob@tools.ietf.org" <draft-ietf-netext-pmipv6-flowmob@tools.ietf.org>
Subject: Re: [netext] #16: requirement for single interface
X-BeenThere: netext@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: cjbc@it.uc3m.es
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 21:22:54 -0000

Hi Pierrick,

Please see inline below.

On Thu, 2013-02-14 at 11:41 +0000, pierrick.seite@orange.com wrote:
> > -----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? 

Yes, that's one possibility.

> 
> 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.]

I'm fine with your proposal. I'll use that text in the next revision of
the draft, unless people disagree.

Carlos

> 
> > --
> > -------------------------------------+---------------------------------
> > -
> > -------------------------------------+---
> >  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.
>