Re: [5gangip] FW: New Version Notification for draft-xyx-5gip-ps-01.txt

Ca By <cb.list6@gmail.com> Tue, 23 May 2017 15:51 UTC

Return-Path: <cb.list6@gmail.com>
X-Original-To: 5gangip@ietfa.amsl.com
Delivered-To: 5gangip@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3B244129BAE for <5gangip@ietfa.amsl.com>; Tue, 23 May 2017 08:51:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.449
X-Spam-Level:
X-Spam-Status: No, score=-2.449 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham 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 Z-5a881HkPpU for <5gangip@ietfa.amsl.com>; Tue, 23 May 2017 08:51:47 -0700 (PDT)
Received: from mail-yw0-x22c.google.com (mail-yw0-x22c.google.com [IPv6:2607:f8b0:4002:c05::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 695F9129B81 for <5gangip@ietf.org>; Tue, 23 May 2017 08:51:47 -0700 (PDT)
Received: by mail-yw0-x22c.google.com with SMTP id b68so76570668ywe.3 for <5gangip@ietf.org>; Tue, 23 May 2017 08:51:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=X8HQs/2VjWYTga6gs4wyRmEhouSWQKgBNZ0eF9tniiU=; b=IBarjNvWmFi3ZrtW8zuIMoqUpuqORXXqkZ7PoMb6RquTbvn4cpNwA+b44djXZn7yvQ 0grIp+a6LM0h6kY0KWpiOVkbqAtTDyINIwOsXVL17KPNUvjIoAih4+OOdig60IWwXc0z FfCLPFbuiD8/r1/6kPDs1praFq4wbTN1MdCrze5SJerxFjFPmspw2Utls2RrDrxV2KzX l8ieMErMsCt6r9hWaNn5TpARiKnMlGIcy3mDca+8Na7nNeD79mwptk4uKyFJ+1OAm0JU JNMGJUxWbGEfCSTV3aNBkcUULDkEfy7OAuVTxA+wRz3MSWh4eooaVE2+X2qNgj+8xSWe nNvA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=X8HQs/2VjWYTga6gs4wyRmEhouSWQKgBNZ0eF9tniiU=; b=FuhQ8qxTr4+4B/cxIdK5izA6Eq9eITr6y1zxSlFTI+R9BZQIb7hjjyNJL3W5b6mxxH XJHri6IM1UM7pNSpi56dkBdo1Yty2fpjBtRj6F/fSs23KzVLxKk0trWBeG2TXVDIu57+ L3zln/TTKlT+z0eJpeztV5Xft/y4zPzXtqs7ZF9Lbsf7oB9PJqEDwPRamkJM6b167wmI waS88nr+8OJLTAos+5mrgQDPGHvRdoG6sBXIYuYS9PoXG9q21CtVAouqy5hrKgcLTgjQ lTztGFwodHZPMPIq922Sz5phqG2DahOPJ/WTi7acHlh4TDHluokdFw7kGpKdUJLhfPq4 nXow==
X-Gm-Message-State: AODbwcBlsESji9z/4dNo+TTkiEcWVDgebE4i7jqYllzg77Q7mT7g48Ac K0ilsNaN4/2Jv/t4jyshnD+NQgsb/Wx9utc=
X-Received: by 10.129.161.210 with SMTP id y201mr23149304ywg.116.1495554706556; Tue, 23 May 2017 08:51:46 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.129.153.208 with HTTP; Tue, 23 May 2017 08:51:45 -0700 (PDT)
In-Reply-To: <1765af8f1375483dba56391633ebb4d5@HE105831.emea1.cds.t-internal.com>
References: <149547735610.22634.10661693302211465600.idtracker@ietfa.amsl.com> <CAC8QAcdiCsxRT7_ube47q5YiAdkBP9-jC7AyLWXQaGR4vAboRQ@mail.gmail.com> <1765af8f1375483dba56391633ebb4d5@HE105831.emea1.cds.t-internal.com>
From: Ca By <cb.list6@gmail.com>
Date: Tue, 23 May 2017 08:51:45 -0700
Message-ID: <CAD6AjGSYJVjnBkA0oTO49=ApPeHQBK=z5JPadBtujoP0_9iL8g@mail.gmail.com>
To: Dirk.von-Hugo@telekom.de
Cc: 5gangip@ietf.org
Content-Type: multipart/alternative; boundary="001a114f8f4606cdbf055032f762"
Archived-At: <https://mailarchive.ietf.org/arch/msg/5gangip/XyAv1vXTqDd0kqtVtbZSyHCF96Q>
Subject: Re: [5gangip] FW: New Version Notification for draft-xyx-5gip-ps-01.txt
X-BeenThere: 5gangip@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Discussion of implications of the upcoming 5th Generation \(fixed and\) Mobile communication systems on IP protocols." <5gangip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/5gangip>, <mailto:5gangip-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/5gangip/>
List-Post: <mailto:5gangip@ietf.org>
List-Help: <mailto:5gangip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/5gangip>, <mailto:5gangip-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 May 2017 15:51:50 -0000

Folks,

I remain very skeptical about the value of this group's collected
protocols.  The scope overlaps with work in the 3GPP, contradicts work in
the 3GPP, and the proposed ideas here are not obviously high value or fit
for the internet or mobile networks.

Don't get me wrong, i am not in love with the 3GPP and i think there is a
lot to improve on many fronts.  But,  MAMS and LISP and ILA are not on the
short list of approaches i would hold up the 3GPP and say this is a better
way.  In fact, MAMS as a proxy and ILA as a NAT are exactly the legacy
telco stuff i would expect the IETF to work against in favor of a more
secure, more salable, and more end-to-end internet.

AFAIK, FMC is already solved today.  My very own iPhone can make calls on
WiFi, LTE, and switch between the 2 -- this is all standard 3GPP work from
IMS. When i sit outside my house with bad wifi, the UE bounces between WiFi
and LTE endlessly, but this unstable network does not interrupt me
streaming Youtube.  So, i just don't see a problem to be solved here,
especially if it incurs a great deal of complexity and state and
signalling.  That said, MIF and Happy Eyeballs both address this issue of
performance and network selection -- and i would strongly suggest the UE is
in the best position to determine network quality and user experience.

I can't get over it this reduction: MAMs adds a proxy and ILA adds a NAT.
I just don't think that is architecturally wise in 4G or 5G.   They just
can't  scale in a gigabit broadband 5G usecase [which is the usecase that
pays the bills, not the pie in the sky stuff], and don't add meaningful
value, and simply detract value at scale.  Also, ILA and MAMs takes a lot
of work on the UE.  Getting changes into the UE is very hard, it took 10
years from the standardization of IMS to get functional IMS client (VoLTE)
deployed at scale.

Finally, the 5G ship has already sailed.  Many network are "launching 5G"
this year, and more networks (including the one i work at ) are committed
to launching "real 5G" in the next 2 to 3 years.  None of the work in this
group is within that 5G scope AFAIK. So, it may be most appropriate to
carry on the effort at 6G to avoid folks getting confused.

I still hold out hope for ILNP to replace the mobility core at some future
date, the radio network just does a simple authentication and that is all.
But, that is my own dream of a simpler world :)  I would suggest the
standard we look for in this group is:  what can we remove from 3GPP 5G /
6G, not what we can add.  How does the work in this group reduce NET
signalling and user-plane modification from the 3GPP steady state?  How is
that quantified?

CB



On Tue, May 23, 2017 at 2:53 AM, <Dirk.von-Hugo@telekom.de> wrote:

> Dear all,
>
> We have updated the PS draft on 5G IP issues regarding the planned BoF in
> Prague.
>
> Please check whether we have addressed the comments correctly and continue
> to discuss this towards further improvement.
>
> Thanks a lot – also on behalf of Roland, SungHoon, and Behcet
>
>
>
> Best Regards
> Dirk
>
>
>
> ---------- Forwarded message ----------
> From: <internet-drafts@ietf.org>
> Date: Mon, May 22, 2017 at 1:22 PM
> Subject: New Version Notification for draft-xyx-5gip-ps-01.txt
> To: Behcet Sarikaya <sarikaya@ieee.org>, Tom Herbert <tom@herbertland.com>,
> Roland Schott <roland.schott@telekom.de>, SungHoon Seo <sh.seo@kt.com>,
> Roland Schott <Roland.Schott@telekom.de>, Dirk von Hugo <
> dirk.von-hugo@telekom.de>, Satish Kanugovi <satish.k@nokia.com>
>
>
>
> A new version of I-D, draft-xyx-5gip-ps-01.txt
> has been successfully submitted by Behcet Sarikaya and posted to the
> IETF repository.
>
> Name:           draft-xyx-5gip-ps
> Revision:       01
> Title:          5G IP Access and Session Management Protocols
> Document date:  2017-05-22
> Group:          Individual Submission
> Pages:          14
> URL:            https://www.ietf.org/internet-drafts/draft-xyx-5gip-ps-01.
> txt
> Status:         https://datatracker.ietf.org/doc/draft-xyx-5gip-ps/
> Htmlized:       https://tools.ietf.org/html/draft-xyx-5gip-ps-01
> Htmlized:       https://datatracker.ietf.org/doc/html/draft-xyx-5gip-ps-01
> Diff:           https://www.ietf.org/rfcdiff?url2=draft-xyx-5gip-ps-01
>
> Abstract:
>    This document builds upon 5G IP issues work and - based on a
>    simplified 5G system architecture - attempts to make the case for a
>    possible set of new protocols that need to be developed to be used
>    among various virtualized functions in a 5G network.
>
>
>
>
> Please note that it may take a couple of minutes from the time of
> submission
> until the htmlized version and diff are available at tools.ietf.org.
>
> The IETF Secretariat
>
>
>
> _______________________________________________
> 5gangip mailing list
> 5gangip@ietf.org
> https://www.ietf.org/mailman/listinfo/5gangip
>
>