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

Behcet Sarikaya <sarikaya2012@gmail.com> Mon, 29 August 2016 15:00 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 275E212D613 for <dmm@ietfa.amsl.com>; Mon, 29 Aug 2016 08:00:57 -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 aSf7hqcGDDcC for <dmm@ietfa.amsl.com>; Mon, 29 Aug 2016 08:00:53 -0700 (PDT)
Received: from mail-ua0-x22c.google.com (mail-ua0-x22c.google.com [IPv6:2607:f8b0:400c:c08::22c]) (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 6565712D0BC for <dmm@ietf.org>; Mon, 29 Aug 2016 08:00:53 -0700 (PDT)
Received: by mail-ua0-x22c.google.com with SMTP id i32so79893736uai.2 for <dmm@ietf.org>; Mon, 29 Aug 2016 08:00:53 -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=ObI5BSJLDzH86yblZm5Svw8yvfFYUUFm0FEfLDFnDVw=; b=IsgQyBIjJDYQJE1P4uol9GnphMZ3vE3MP8FwykX9hbdRBZDZ7icLoeKIefhzsVejCA z4W2h5F8Rp28nVJM/3LU8up1u9a6uc38bdRnWtqdzUHrgGiNNW55z+iJjDkZSUDuiALZ g0llQkPK/46dx00DDTRk7m2/CcnEIaL5sNMi/Vx/v0fMDa+0clVZBRzQMfxcle5+cAm5 6GS11DyYUjlmgQmgOpw55xfzXuSPC789inPLmurrXSEftkMExpgYtLTPp2mm8QjvPeYb 1iyL0dGo/lfePbGnHLUUf6n10kcKiuotyCPZ2dlpq52gut5bAPcQJdEHGQAxpOxAtv8/ ntlw==
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=ObI5BSJLDzH86yblZm5Svw8yvfFYUUFm0FEfLDFnDVw=; b=LWZxu6AfV4wCAnsfxXA7r4Nvcf5/9QtMmL/HG/P/hJzC7Y4fFQ3pX0pr4q68Thpjb7 Garm6FRpI5vbHYm8uk4Ug0J7v+Dqaq8lUPnKfnTMUj+bqlEfzsPYVrGY9NvsZ9Q8lsNJ xw55gQ5PNC+rDzR6TPks8Bc8l/pHR8oEFFwLMokUNo+Mbg2ehaFJIu3/dY2aL0C47zuK A1fATKH/LqXQ31+JUcxV3Hd7UkPsKalJOzeaieFilqMuJs1qygL4zvihqUKbeF9RsV0b 2BvSc3yhBrhVzZpuwta8ClZ5ujFO2GUjmlVbnL3+i2qcRQhq0thVk5p5j4Q1Cg+oEhkE KUEQ==
X-Gm-Message-State: AE9vXwNyqWLKB+TiMo0o+PQ1qM4QtXasMha95Is2TIklE+bsDjWbBTQEGGuUqQlpRMByb1DvL6VtvTsNHhn5Mw==
X-Received: by 10.159.37.106 with SMTP id 97mr10014796uaz.27.1472482852470; Mon, 29 Aug 2016 08:00:52 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.176.82.182 with HTTP; Mon, 29 Aug 2016 08:00:52 -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:00:52 -0500
Message-ID: <CAC8QAcegU5=sURx3ctL8NTLLFOuMohJf8ee8GsFvY5XWC1V-sw@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/Q_T_sezyvAl1HG0g-hKeC6dCApQ>
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:00:57 -0000

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

I think that 3GPP already implemented control and data plane separation.

Regards,

Behcet
>
>
> 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
>