Re: [DMM] Questions on draft-matsushima-stateless-uplane-vepc-02

Behcet Sarikaya <sarikaya2012@gmail.com> Fri, 23 May 2014 16:23 UTC

Return-Path: <sarikaya2012@gmail.com>
X-Original-To: dmm@ietfa.amsl.com
Delivered-To: dmm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E541C1A06D4 for <dmm@ietfa.amsl.com>; Fri, 23 May 2014 09:23:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.75
X-Spam-Level:
X-Spam-Status: No, score=-1.75 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=no
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 uk-8kmJUCgHF for <dmm@ietfa.amsl.com>; Fri, 23 May 2014 09:23:39 -0700 (PDT)
Received: from mail-yk0-x22b.google.com (mail-yk0-x22b.google.com [IPv6:2607:f8b0:4002:c07::22b]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 018DD1A0698 for <dmm@ietf.org>; Fri, 23 May 2014 09:23:38 -0700 (PDT)
Received: by mail-yk0-f171.google.com with SMTP id 142so4159939ykq.2 for <dmm@ietf.org>; Fri, 23 May 2014 09:23:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:reply-to:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=od8NLY73ZJ4TubCKzxjxGzm737NBIbc2Dr3eDbczJrg=; b=I0ywgMEUgXXBB2tlrZhtNC4Qbo55OdX4J/Dh9vSNDh7yrkremBl57pmpyOvRoR/HQ0 o5j7OJtOVriVoMbuKWfhSvRrwgUWZVVVQjq0Aq/LueBvUMGAmbFf7aVtkb1LijnnW2Kv 9tsdSsKyQ6csoc/kmDVfnBVo22h2D7I4dTnLMkc9MWRZujPUtKMcgMCx3g9iWkT4FzpI RcvaYkHhzruqvGFJv0b7ETERhDPKmHKgbff2ZczN1ngezTOKh9wErGCGYU0PZeg6RYld 8w21JSLkLEcCXzMSWbNHFjJ959ZALPaJAK0g9aeoLov2zATVrQyepOYpORd9v9oddN1w wgPQ==
MIME-Version: 1.0
X-Received: by 10.236.137.243 with SMTP id y79mr3530696yhi.31.1400862216843; Fri, 23 May 2014 09:23:36 -0700 (PDT)
Received: by 10.170.126.18 with HTTP; Fri, 23 May 2014 09:23:36 -0700 (PDT)
In-Reply-To: <CAFwJXX4JwoLKcu-AqK+TsqNX_Ywvahc1kciF3DeD+ydWP1genw@mail.gmail.com>
References: <CAC8QAcf-__v4qR+Z2Zh2az+W3BTR_Bu8JkZxbWirHHw7zKm2WQ@mail.gmail.com> <CAFwJXX6FN2TRt4RUafDEw0VSPapVHZzWBP81k6aEr5reUh+vvg@mail.gmail.com> <CAC8QAcfhxvSDH-NoaFeuCuWQC5JudLq1h8Xj2No0i5bAd_MPqA@mail.gmail.com> <CAFwJXX5xUNXjjmtN5PuCLFGHsfZL-mvBVjRfbAnGdrc3wvqL0g@mail.gmail.com> <CAC8QAcewzM6YLu5t+XhUQwpmjCZNMRoNbNdQ_ekOhtgqHHaiNA@mail.gmail.com> <CAFwJXX7Eco5UC0Yznr3t1be_1FCiPC5Z5sNtbaPCs5n_r01NQA@mail.gmail.com> <CAC8QAccCJboVGDDy8yYs238MX2x049StN3ebjE8_RVC4W4cLCg@mail.gmail.com> <CAFwJXX4JwoLKcu-AqK+TsqNX_Ywvahc1kciF3DeD+ydWP1genw@mail.gmail.com>
Date: Fri, 23 May 2014 11:23:36 -0500
Message-ID: <CAC8QAcdfHOLFivoTyYYwCLpwEZYHiY8EVsV+jiHvgRZW3yUE8A@mail.gmail.com>
From: Behcet Sarikaya <sarikaya2012@gmail.com>
To: Satoru Matsushima <satoru.matsushima@gmail.com>
Content-Type: text/plain; charset="UTF-8"
Archived-At: http://mailarchive.ietf.org/arch/msg/dmm/RPYwXequuPJ-EH8vnfsj4Pol54k
Cc: "dmm@ietf.org" <dmm@ietf.org>
Subject: Re: [DMM] Questions on draft-matsushima-stateless-uplane-vepc-02
X-BeenThere: dmm@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: sarikaya@ieee.org
List-Id: Distributed Mobility Management Working Group <dmm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmm>, <mailto:dmm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dmm/>
List-Post: <mailto:dmm@ietf.org>
List-Help: <mailto:dmm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dmm>, <mailto:dmm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 23 May 2014 16:23:40 -0000

Hi Satoru,

It seems most issues are resolved, except one below.

Regards,

Behcet

On Fri, May 23, 2014 at 3:39 AM, Satoru Matsushima
<satoru.matsushima@gmail.com> wrote:
> Behcet, thanks for clarifying more clearly. :)
>
>
> On Fri, May 23, 2014 at 4:15 AM, Behcet Sarikaya <sarikaya2012@gmail.com>
> wrote:
> -- snip --
>
>>
>> >
>>
>> > Ah, I see what you mean. Yes, I'm sure that RR/RS just only know about
>> > routes, nor whole mobility information exists. When I see a node which
>> > plays
>> > MME role, the node could also be a BGP speaker to export the mobility
>> > info
>> > transformed to the routes.
>> >
>>
>> So MME should be BGP speaker?
>> If not then what would happen?
>>
>
> Precisely, say MME, which 3GPP defined mobility management entity, doesn't
> have the BGP function. IMO, If the entity can be coexist with BGP in a
> single node, an interface for exposing/retrieving mobility information would
> be required between them.
>
>
>>
>> > What do you mean by "topologically incorrect"?
>> > Is that the assigned prefixes are disordered to be aggregated?
>> >
>>
>> Yes. UE moves to another EPC-E which supports a different prefix than UE
>> has?
>> You need to keep host-based prefixes as routes, is there another way?
>>
>
> In the draft, as long as an UE keeps same prefix during hand-over among
> EPC-E routers, those routers belong to a same group that is expected to
> preserve same prefix for the UE. It should be initial attach when the UE is
> attached to different EPC-E and assigned different prefix from previous one.
> Please read section 3.3 and 3.4 of the draft.
>

Attach is OK but I am talking about handover. In Section 3.4 you say:
Thus, UE's address
   is unchanged even after handover.

I don't understand your statement
those routers belong to a same group that is expected to
 preserve same prefix for the UE.

I think you mentioned this before in another conversation that EPC-E's
will be assigned prefixes based on geographical division. If a UE
moves to a different region, how could the routers preserve the same
prefix for the UE without host routes or host prefixes?

Regards,

Behcet
> cheers,
> --satoru