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

Satoru Matsushima <satoru.matsushima@gmail.com> Fri, 23 May 2014 08:39 UTC

Return-Path: <satoru.matsushima@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 6A4871A03DA for <dmm@ietfa.amsl.com>; Fri, 23 May 2014 01:39:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] 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 xhRY6T5ruOys for <dmm@ietfa.amsl.com>; Fri, 23 May 2014 01:39:24 -0700 (PDT)
Received: from mail-yh0-x235.google.com (mail-yh0-x235.google.com [IPv6:2607:f8b0:4002:c01::235]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5C0891A03D9 for <dmm@ietf.org>; Fri, 23 May 2014 01:39:23 -0700 (PDT)
Received: by mail-yh0-f53.google.com with SMTP id i57so3945163yha.40 for <dmm@ietf.org>; Fri, 23 May 2014 01:39:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=Sq8fIVIw/8tQWZJDJhlO9cpdAvQkyNPJwPzPd+ta+Rc=; b=RQ2LC/Q0CN4rMG7EiixP460WQguMDKnQ0gvS9D15Cblr9AQCMmPh75AQJXeo5wNUQ9 KpBL/I9+tBhf2zBDC5isAOYJgDTPC7ApG1kFsSpE9nmHxKqtaz2lJk6KnwjkwIiRXpR3 tNsfWmZuOi7qRffzYLr5fmGqPWUhieRjXzpPCVTeARVTWKGOB+Oe+E9LhXEBGTMQhLBk EHDslbXQpF3Bkc0v3bMnD1dptqF0++FR/nUbqkv1Swwx2WZKZJuh//iS9dVYNK3V/rmB hVGF4l3NwUBE9fL0TJXxABxjiTxYouxkK2NhWBXbzpoV2K6QYfcoXroYe+t1+I0dunGN /rDA==
MIME-Version: 1.0
X-Received: by 10.236.114.193 with SMTP id c41mr1602995yhh.156.1400834360928; Fri, 23 May 2014 01:39:20 -0700 (PDT)
Received: by 10.170.155.213 with HTTP; Fri, 23 May 2014 01:39:20 -0700 (PDT)
In-Reply-To: <CAC8QAccCJboVGDDy8yYs238MX2x049StN3ebjE8_RVC4W4cLCg@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>
Date: Fri, 23 May 2014 17:39:20 +0900
Message-ID: <CAFwJXX4JwoLKcu-AqK+TsqNX_Ywvahc1kciF3DeD+ydWP1genw@mail.gmail.com>
From: Satoru Matsushima <satoru.matsushima@gmail.com>
To: sarikaya@ieee.org
Content-Type: multipart/alternative; boundary="20cf303b3fe778ede304fa0d2aa7"
Archived-At: http://mailarchive.ietf.org/arch/msg/dmm/xToo6c6T3IrXRQjqoRQyzLQnmb4
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
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 08:39:25 -0000

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.

cheers,
--satoru