[DMM] Overall review on "draft-bogineni-dmm-optimized-mobile-user-plane-00"

Satoru Matsushima <satoru.matsushima@gmail.com> Wed, 06 June 2018 06:57 UTC

Return-Path: <satoru.matsushima@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 500E7130EBA; Tue, 5 Jun 2018 23:57:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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 wMRfcfDEzmsA; Tue, 5 Jun 2018 23:57:14 -0700 (PDT)
Received: from mail-pl0-x235.google.com (mail-pl0-x235.google.com [IPv6:2607:f8b0:400e:c01::235]) (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 D40EF130EB7; Tue, 5 Jun 2018 23:57:11 -0700 (PDT)
Received: by mail-pl0-x235.google.com with SMTP id i5-v6so3190489plt.2; Tue, 05 Jun 2018 23:57:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:content-transfer-encoding:mime-version:date:subject:cc:to :message-id; bh=u4ncOb9dCJt9L8jgaIuyfVTMXbvaZ2whjF77Dp6H2no=; b=gDoDu2Abx5YGnbJmZeLNpgRIl1p+N67vofDO+ZL5YpHSnQESLgEiKMGTQUiEoGyCSg Vq6PuLSQ1z4jqHAeW0KhER9p+O3sxHtqiJHRva84w9CK62195ld0bWm00ZIWg/EbPRVz HArFjfGW2/GmJU4S5h9ORnBWkRfd2eY5ZBexWz88ih13E39tjjNQzz2CTfa3GrdrigrW A+FNEQMomuFVLiBC8vTMX8oVEQowZQ0mrZdqD+/rkeUkJZSuXhTHfFOhBHrqizjWzm9h io2ziuie5MSbOnDlj6LYayZq/aPc/TPHyo5k+MVSAXZZH6RbCQaP9YvcBMMSQ6P5iwqW BikQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:content-transfer-encoding:mime-version:date :subject:cc:to:message-id; bh=u4ncOb9dCJt9L8jgaIuyfVTMXbvaZ2whjF77Dp6H2no=; b=rvuyJIQl/JjVSs3MkHQNyjRGc9JswS754fJZU/lTaH/edMSELdlGfFVxJAzczeju3O mKQOknm7gNtPan+rAWoKLTsB/yhkQXjelCGTwK9SJX+bBy4WqOjMQaltVYlbz/dZKQ3R TvRNfkQyhw4TMU+2g9OqaRUkEFeyAMhGO4vYcwOeMVP6lkFcTv53Rgr/49WVqGcSUFnc W2DfB3Zfaei8yQI+Qq4F13FjxxEna07gWgVyohW/xg99cphjLcNuO9kF/eWHLMa85ftt fnI8aSgovYkYraKqWXyXhv//gIo/4W5qiD2Pk0gQVF2s5d0cOkvAgMHR74DgEffs9Yeg HCqQ==
X-Gm-Message-State: APt69E1Kh7qeKYtJKVVMrTwggUu/uYtggUlPTCfmDLIFAXzaIU/EDAh7 75vsR5GvrVEiK00b72oAWXwW+hk0
X-Google-Smtp-Source: ADUXVKK8rst3jv9hBzBKaSjxVVbYSSwVlBVmuNuyrZ4e/r+6i/xMc7DNDg11phTRPz7/j7zLi1facA==
X-Received: by 2002:a17:902:bd04:: with SMTP id p4-v6mr2051051pls.180.1528268230946; Tue, 05 Jun 2018 23:57:10 -0700 (PDT)
Received: from [10.217.59.188] ([202.45.12.165]) by smtp.gmail.com with ESMTPSA id e16-v6sm11186782pff.185.2018.06.05.23.57.08 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 05 Jun 2018 23:57:09 -0700 (PDT)
From: Satoru Matsushima <satoru.matsushima@gmail.com>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 11.3 \(3445.6.18\))
Date: Wed, 06 Jun 2018 15:57:06 +0900
Cc: draft-bogineni-dmm-optimized-mobile-user-plane@ietf.org
To: dmm <dmm@ietf.org>
Message-Id: <C80BC1DB-4287-412D-8688-62AA08A19EC0@gmail.com>
X-Mailer: Apple Mail (2.3445.6.18)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmm/0lO0rr8oW89iv46cgxv9qjGEdqY>
Subject: [DMM] Overall review on "draft-bogineni-dmm-optimized-mobile-user-plane-00"
X-BeenThere: dmm@ietf.org
X-Mailman-Version: 2.1.26
Precedence: list
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: Wed, 06 Jun 2018 06:57:19 -0000

Dear Kalyani, and the draft authors,

Thank you so much for working on this I-D which brings much information regarding user plane protocols in IETF. It looks very promising work on IETF side corresponding to the user plane protocol study work (FS_UPPS) in 3GPP CT4.

Since I’m in the loop in the offline discussion of updating the draft, let me leave to bring detail comments on this version but instead here I’d bring following my overall comments on the draft as the rapporteur of FS_UPPS on 3GPP side.


1. Clarification on the TR/TSes

As the LS(*) pointed the User Plane protocol and several User Plane related specs in 3GPP, clarifying those specs in terms of user plane are highly appreciated. As I presented in London(**), the approach for this study in CT4 will be investigation and comparison for the candidates protocols including existing protocol that needs criteria to do that. Clarifying 5G specs in terms of user plane based on IETF expert’s analysis would be very helpful to figure out that criteria.

In CT4 side, we don’t have prefer logistic for the outcome of the clarification. The I-D has just a section of overview of 5G system but it looks quite a document already so that another concise clarify focused document in Internet Draft style sounds make sense to me. 


2. Contents organization

The I-D contains SRv6, LISP and ILA as the candidate user plane protocols. Those protocols seem to have each characteristics and certain level of impacts to the 3GPP 5G architecture. However it was difficult to find those features and impacts when I went thorough the draft. Though the LS asks DMM to provide any information regarding User Plane protocol, it would be nice at least if you can provide over-the-wire packet format, for instance, with the features of each protocol. And it would be followed by expected impacts to the 3GPP control plane of each candidates, as I said in London. In addition to that, distinguishably describing more impacts to the architecture beyond Release 15 would be much helpful to clearly understand on what those candidates require the architecture to be changed, as INT AD, Suresh, stated in London if I recall correctly. It would be also highly appreciated if those can be found out at a glance from the draft. That make us easy to digest it.

Please note that it does not mean the candidates need to be in apple-to-apple evaluation. It just needs the clear differences between the candidates to be highlighted in terms of user plane, control plane and architectural impact.


3. Use of term ‘Optimization'

The word “optimized” in the draft title seems ambiguous on that optimize for what. If you try to introduce how those candidates optimize something, it would be better to make clear the target of the optimization. But again the LS asks any information on user plane, the I-D doesn’t necessarily describe it. 

(*) https://datatracker.ietf.org/liaison/1572/
(**)https://datatracker.ietf.org/meeting/101/materials/slides-101-dmm-study-on-user-plane-protocol-at-3gpp-00


Hope that helps, and I’m happy to cooperate together on the user plane study on both IETF/3GPP sides.

Best regards,
--satoru