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

Ca By <cb.list6@gmail.com> Wed, 24 May 2017 12:32 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 EB63A129C26 for <5gangip@ietfa.amsl.com>; Wed, 24 May 2017 05:32:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.448
X-Spam-Level:
X-Spam-Status: No, score=-2.448 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, URIBL_BLOCKED=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 XIPL8WgXUggK for <5gangip@ietfa.amsl.com>; Wed, 24 May 2017 05:32:13 -0700 (PDT)
Received: from mail-yw0-x232.google.com (mail-yw0-x232.google.com [IPv6:2607:f8b0:4002:c05::232]) (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 C8C28129C09 for <5gangip@ietf.org>; Wed, 24 May 2017 05:32:12 -0700 (PDT)
Received: by mail-yw0-x232.google.com with SMTP id b68so88296167ywe.3 for <5gangip@ietf.org>; Wed, 24 May 2017 05:32:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=Tb7aGk2sH8fnmMUyzB3EclS5seBdF9XZzJMv63bqch8=; b=bh0Bdi/Upl/Trjya+SY1ZFGpbfwxU01JMlD52fJ4wHVhMMFzhmoq2dnda/i4a3NG3I LGaMl0/aauL0t635awEteGdz9K+DrtN9O22mwnR0LSyGG0RZ5BE5A9rIcKI7jchU+wZP 7lA53Wu+7JYA8bxn+tW1GdSnDR8dEma5+BE5bcK5UB7ZdnxXdjPWyf8m4yXaKJKXmqdm N3PXmOCLs2/uUzq82QNasdEW6pzCcH3o+Kag1N5Uod3b8EGYnHA8eEFhLCAQn0m6bWjZ mb5k594h3XfFeEbRBcbzKbfJ4CBYf2zHR31jS0PquhTy6QoMav+3UWvUWbWWsIbr7ycP 8+rw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=Tb7aGk2sH8fnmMUyzB3EclS5seBdF9XZzJMv63bqch8=; b=EpMcq/7PBefivbJLDquCq4lmxjoPOrN4jPPVDBeEsFC503Emwpc/m0viGZ0dGB+8HE Z3OIL0Cw47nCL9z9o3fH51cqfEJN1I/rScBs0OA2vRNiNmmHR5HNsb7KhH5yZhOOtihE ac6fgElbgUZtR3UMQuTZ+NXC1eqUyJj3GW/o8QggiPFYdNaitHXt09mchyzAZ8ns9xpn yuVoXWaSBqoXTz3EqhGpS8DUA5hbbzzUkNjPfqV9XZ8yvdLluDvSaKjnnYS+lcUHAWYY J+HVx+DVeQzCYCiLdNPo+EQnmOPRtDWbVlFXbkyxQkAFQj7uvUBVlqN2tDa2EFsXW2If yi2w==
X-Gm-Message-State: AODbwcDpDGI0IDX6MSK9aYei+AqkdYKg0KERMAiVkxob8WWkcdJr0EfQ akAAPP6wOR0yrpqH/qglsSrGCgpuiQ==
X-Received: by 10.129.161.210 with SMTP id y201mr26565185ywg.116.1495629132073; Wed, 24 May 2017 05:32:12 -0700 (PDT)
MIME-Version: 1.0
References: <149547735610.22634.10661693302211465600.idtracker@ietfa.amsl.com> <CAC8QAcdiCsxRT7_ube47q5YiAdkBP9-jC7AyLWXQaGR4vAboRQ@mail.gmail.com> <1765af8f1375483dba56391633ebb4d5@HE105831.emea1.cds.t-internal.com> <CAD6AjGSYJVjnBkA0oTO49=ApPeHQBK=z5JPadBtujoP0_9iL8g@mail.gmail.com> <CALx6S35GzM7Kmj9C80VN4TZNZZjYwLWXPpZpbPD0gXS-74Va9g@mail.gmail.com>
In-Reply-To: <CALx6S35GzM7Kmj9C80VN4TZNZZjYwLWXPpZpbPD0gXS-74Va9g@mail.gmail.com>
From: Ca By <cb.list6@gmail.com>
Date: Wed, 24 May 2017 12:32:00 +0000
Message-ID: <CAD6AjGRwK+ikUeytA=H64VMO1o1GkPVV4e9q3CaSi0xNi0xHAw@mail.gmail.com>
To: Tom Herbert <tom@herbertland.com>
Cc: 5gangip@ietf.org, Dirk.von-Hugo@telekom.de
Content-Type: multipart/alternative; boundary="001a114f8f462210b90550444b29"
Archived-At: <https://mailarchive.ietf.org/arch/msg/5gangip/euleV-lZ_a8xqNTc9k4OUxNAZ2Y>
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: Wed, 24 May 2017 12:32:16 -0000

On Tue, May 23, 2017 at 1:32 PM Tom Herbert <tom@herbertland.com> wrote:

> On Tue, May 23, 2017 at 8:51 AM, Ca By <cb.list6@gmail.com> wrote:
> > 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.
>
> Hi Ca,
>
> Can you explain why you think ILA doesn't scale to gigabit broadband?
>
> ILA requires no changes to UEs and it's already being deployed in
> datacenters at higher bandwidths than gigabit. It's more efficient
> than encapsulation in both on the wire overhead and processing
> overhead.
>
> Tom
>

Tom -- as a network operator, my ideal scenario just moves the packets.  To
that end, i would like to remove the anchor / touchpoint.

The scaling comment is that any anchor needs to scale to N where N is some
set of users total throughput. This is why ILNP appeals to me and ILA looks
like more of what we already have today with less functionality.


> > 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
> >>
> >
> >
> > _______________________________________________
> > 5gangip mailing list
> > 5gangip@ietf.org
> > https://www.ietf.org/mailman/listinfo/5gangip
> >
>