Re: [DMM] DMM FPC I-D - Implementation

Behcet Sarikaya <sarikaya2012@gmail.com> Mon, 29 August 2016 15:15 UTC

Return-Path: <sarikaya2012@gmail.com>
X-Original-To: dmm@ietfa.amsl.com
Delivered-To: dmm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 84DF012D13E for <dmm@ietfa.amsl.com>; Mon, 29 Aug 2016 08:15:06 -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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 NMhWx1fBD0TE for <dmm@ietfa.amsl.com>; Mon, 29 Aug 2016 08:15:05 -0700 (PDT)
Received: from mail-ua0-x22e.google.com (mail-ua0-x22e.google.com [IPv6:2607:f8b0:400c:c08::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 21E8F12D0BC for <dmm@ietf.org>; Mon, 29 Aug 2016 08:15:05 -0700 (PDT)
Received: by mail-ua0-x22e.google.com with SMTP id k90so250990471uak.1 for <dmm@ietf.org>; Mon, 29 Aug 2016 08:15:05 -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:from:date:message-id :subject:to:cc:content-transfer-encoding; bh=sd+UYnYTczy+iIEw8e7Kd9J9O9XrR3WaHfpoNkUN/Ag=; b=yjf6Z4FwF3mb71dhc2zMxjFxOXDXIGIbWywpfrPi2nVwyEjERsW1huOuP8BbO+ksdZ CPDDlHjBCgEquKdhK9muRuII+BXJqsOcUa5At0mx7U+TUsug7N12TMfMitSiHjj66B1N Db9Qi3UCwviHrxcrjcP6uObIhIm4nd7DB7j4SfWrxJIgODheXKya/3qkinR/3IV4Edkf GuGBIuS8oXVndcDaSuTTIaLYCX9vO4I4g1SqVyuovQOjjHf+NB5d/KqinmK/bTwoHB/m m2hmk0uw4O3qbVtuN2IJEQSsyTKTDcyIC9HXS6d4Z77yV8h33gXVuRlfHshRc5clLdLI XUAQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:reply-to:in-reply-to:references :from:date:message-id:subject:to:cc:content-transfer-encoding; bh=sd+UYnYTczy+iIEw8e7Kd9J9O9XrR3WaHfpoNkUN/Ag=; b=kPR5PjKr4J0nY3oLzdwc5PcRrjWmGI6ziizCihfISZ4GKtTEQ/xREswDU+VIruzRmV KM83I5vLT2r7/YsK5AtfBrWSveP2z08Ae0s2nD4SrjE5k6RsnKHFK4fp+AuZSoGg4QJE 6/UquUbzkUHHTbIzGlFYC3cxljqsARo90Rzgeee39qbtWDGnAKMvAD/cRVc/4s4T6TTK EEO0+x8iAEZY7Vh18mtTzghGmx6PXR8h0ssFKz5LHV++VunNpn1SItkSD0fLu6tEdTjF vbhqn5cI+fpjrLgT4QibcPdKIxSXUTUBUEu+aCxIMjE/vEvRLIN2kpp23gla/hSRke4s BRTQ==
X-Gm-Message-State: AE9vXwMyRQNmMqtFJcr2PaxTySjvnp+swaROJAs4C29M2qj/EMcG2q1BXurY+Tq1zDkA7DaIWPwq4fNuQAKKdw==
X-Received: by 10.176.83.123 with SMTP id y56mr6954430uay.4.1472483704198; Mon, 29 Aug 2016 08:15:04 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.176.82.182 with HTTP; Mon, 29 Aug 2016 08:15:03 -0700 (PDT)
In-Reply-To: <bde9d536cf7e4eae84eeaab2b6f7d4d9@plswe13m04.ad.sprint.com>
References: <bde9d536cf7e4eae84eeaab2b6f7d4d9@plswe13m04.ad.sprint.com>
From: Behcet Sarikaya <sarikaya2012@gmail.com>
Date: Mon, 29 Aug 2016 10:15:03 -0500
Message-ID: <CAC8QAcevXzSD__inTt46iKjr72son6gzmX9vsWKycXsuEugu2A@mail.gmail.com>
To: "Bertz, Lyle T [CTO]" <Lyle.T.Bertz@sprint.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmm/7FvmwG8ExZabvcfrp2UzkXbEYS0>
Cc: "dmm@ietf.org" <dmm@ietf.org>, "Lionel.morand@orange.com" <Lionel.morand@orange.com>
Subject: Re: [DMM] DMM FPC I-D - Implementation
X-BeenThere: dmm@ietf.org
X-Mailman-Version: 2.1.17
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: <https://mailarchive.ietf.org/arch/browse/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: Mon, 29 Aug 2016 15:15:06 -0000

As I mentioned in my previous mail, 3GPP already supports control
plane data plane separation, they just call it user plane control
planes.

See:

https://en.wikipedia.org/wiki/System_Architecture_Evolution

I think you are confused by the SDN approaches in the control plane in 3GPP.

However, 3GPP decided not to pursue SDN. But they will pursue NFV instead.

FYI.

Regards,

Behcet

On Fri, Aug 26, 2016 at 3:00 PM, Bertz, Lyle T [CTO]
<Lyle.T.Bertz@sprint.com> wrote:
> All,
>
>
>
> Last week at the Intel Developer Forum in San Francisco (US), Intel and
> Sprint demonstrated a virtual Evolved Packet Core (vEPC) that included,
> amongst other features, a SGW and PGW (3GPP functions similar to MAG and
> LMA).   This software
>
> 1.       Used a Separated Control and Dataplane Node with an intermediate
> SDN Controller – Opendaylight’s Beryllium release.
>
> 2.       Used IETF DMM FPC-v03
> (https://datatracker.ietf.org/doc/draft-ietf-dmm-fpc-cpdp/?include_text=1)
> for communication of some sessions (others were simulated to ensure we met
> the demonstration timelines).
>
>
>
> The Control and Dataplane software performs well (10Gbps down / 3Gbps up for
> 250K users) on a single Intel processor’s *core* based upon the open source
> DPDK libraries from Intel.  The demonstration shows the promise of
> separation of Control and Data planes.
>
>
>
> We had to deviate quite a bit from the version 03 specification to support
> 3GPP but version 04 adds the 3GPP model as an option.  Many of the general
> changes in version 04 are influenced by the implementation.
>
>
>
> Work is already underway to implement version 04 with several internal
> changes, e.g. moving from the Opendaylight MD-SAL (model driven) approach to
> the application driven (AD-SAL) approach, as focus is now on performance.  I
> hope to share more details in the future.  As a part of the final version of
> the FPC I-D we will submit an Implementation Status section in the draft per
> RFC 7942.
>
>
>
> Lyle Bertz
>
> Sprint
>
>
> ________________________________
>
> This e-mail may contain Sprint proprietary information intended for the sole
> use of the recipient(s). Any use by others is prohibited. If you are not the
> intended recipient, please contact the sender and delete all copies of the
> message.
>
> _______________________________________________
> dmm mailing list
> dmm@ietf.org
> https://www.ietf.org/mailman/listinfo/dmm
>