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

Behcet Sarikaya <sarikaya2012@gmail.com> Wed, 21 May 2014 15:58 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 BD6551A073F for <dmm@ietfa.amsl.com>; Wed, 21 May 2014 08:58:28 -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 SA32Sw5usC8d for <dmm@ietfa.amsl.com>; Wed, 21 May 2014 08:58:28 -0700 (PDT)
Received: from mail-la0-x230.google.com (mail-la0-x230.google.com [IPv6:2a00:1450:4010:c03::230]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 703251A0769 for <dmm@ietf.org>; Wed, 21 May 2014 08:58:23 -0700 (PDT)
Received: by mail-la0-f48.google.com with SMTP id mc6so1760447lab.35 for <dmm@ietf.org>; Wed, 21 May 2014 08:58:21 -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=SbZ4JbnYN/3z5/7eF8LDPW4lSKp+0Khv0kIUtt14YOU=; b=0h2m5cPp56UjnxdZMHBedLtH393IljybmpcOgPgfXbTyYj30xorh2kW4a1cYVVImEJ TOsr6p6bvzunHAXF1g0VQbCzmoeQxXBIODZYYhSLfvqUlSlcN9pO0qynDNdKmuLZ/zr7 kUuvxQpwukpxHolTP9Hfb1DELnyJoznjS90Epq9ypdKN9viJseIW9MH26yoiJrFWcjvM 1SN35gKt6CQb2QHBL0oEvTTHM1/MLqhMqi0cPFR3ODmQGYsZDTvOuhLU8yrEd4tplQ0W i3gbLJHeHcs+LC44Ruy0ukEL3p9bT9qkmGfjb9oD4BB9nVyzXIaU1gTsKaM6buCfuXjv UV5Q==
MIME-Version: 1.0
X-Received: by 10.152.4.1 with SMTP id g1mr38591191lag.20.1400687901085; Wed, 21 May 2014 08:58:21 -0700 (PDT)
Received: by 10.114.27.106 with HTTP; Wed, 21 May 2014 08:58:20 -0700 (PDT)
In-Reply-To: <CAFwJXX5xUNXjjmtN5PuCLFGHsfZL-mvBVjRfbAnGdrc3wvqL0g@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>
Date: Wed, 21 May 2014 10:58:20 -0500
Message-ID: <CAC8QAcewzM6YLu5t+XhUQwpmjCZNMRoNbNdQ_ekOhtgqHHaiNA@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/8tZk6wVmBzwnslgOBEfGJSK6PXo
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: Wed, 21 May 2014 15:58:28 -0000

Hi Satoru,

Thanks again.

Please see my replies inline.

Regards,

Behcet

On Tue, May 20, 2014 at 8:47 PM, Satoru Matsushima
<satoru.matsushima@gmail.com> wrote:
> Hi Behcet,
>
>
> On Wed, May 21, 2014 at 1:17 AM, Behcet Sarikaya <sarikaya2012@gmail.com>
> wrote:
> -- snip --
>
>>
>> >
>> >> Referring to Steps 14 and 15 in Figure 4, in Step 14, Route Update (I
>> >> guess BGP Route Update) is initiated by
>> >> which node and is going to which node?
>> >
>> > As you see step 14 in the sequence, any specific node aren't assumed to
>> > initiate routing update on vEPC side, due to the scope of the draft,
>> > EPC-E
>> > router is the receiving node of routing update
>>
>> You mean more than one node can initiate it, my question was which
>> node(s)?
>>
>
> I meant that the draft doesn't mention exactly which node advertise that, it
> could be expected to exist in the vEPC side. But I find that in terms of
> usual BGP operation, that node could be Route-Reflector(RR), or
> Route-Server(RS).
> Just one case would be expected that a set of information which includes an
> endpoint information of tunnel and an UE assigned prefix is informed from a
> mobility management node in the vEPC to RR or RS.
>

Are you sure?
How would RR or RS know about UE mobility?

I was expecting you to say MME?

>
>>
>> >
>> >> In Step 15 you have EPC-E initiating this and it is going towards RTR.
>> >> Why
>> >> is this not sufficient? i.e. since EPC-E
>> >> can detect mobility?
>> >> Why do you need Step 14?
>> >
>> > The reason of the EPC-E advertise route toward RTR is that EPC-E can
>> > aggregate multiple UE's prefixes into less BGP routes as a part of
>> > normal
>> > routing operation within operator's network.
>>
>> You mean host routes are not needed in the upstream BGP routers? How
>> does that work?
>
>
> Yes, host routes are not needed in the upstream routers because aggregated
> routes EPC-E router advertised work well for the upstream routers to send
> out packets toward advertising EPC-E routers.
>

Isn't it kind of host routes? Maybe host prefixes? Otherwise I can not
image how you would route to UEs that are topologically incorrect?

>
>>
>>
>> >Step 14 makes EPC-E not to
>> > detect mobility directly.
>>
>> I understand that.
>>
>> >
>> >> For the uplink traffic from UE, you seem to assume that it is always
>> >> towards RTR. Could it not be directed to
>> >> another UE? What happens in that case?
>> >
>> > When an EPC-E router has a route for destination of the packet from UE,
>> > the
>> > EPC-E router forward the packet to the destination.
>>
>> You mean to another EPC-E?
>>
>
> I just meant that the packets are always forwarded along with the routing
> table of each node.
>

Yes, I think that the packet to another UE would be routed downstream
before reaching the RTR.

> cheers,
> --satoru