IETF Logo Mail Archive

Re: [DMM] Call for adoption of draft-hmm-dmm-5g-uplane-analysis-02 as DMM WG document

Dino Farinacci <farinacci@gmail.com> Wed, 21 November 2018 16:56 UTC

Return-Path: <farinacci@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 5DE4A130E02 for <dmm@ietfa.amsl.com>; Wed, 21 Nov 2018 08:56:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.098
X-Spam-Level:
X-Spam-Status: No, score=-0.098 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=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 DyvYfxcLxxr5 for <dmm@ietfa.amsl.com>; Wed, 21 Nov 2018 08:56:44 -0800 (PST)
Received: from mail-pl1-x629.google.com (mail-pl1-x629.google.com [IPv6:2607:f8b0:4864:20::629]) (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 2F821130DF1 for <dmm@ietf.org>; Wed, 21 Nov 2018 08:56:44 -0800 (PST)
Received: by mail-pl1-x629.google.com with SMTP id v1-v6so6339643plo.2 for <dmm@ietf.org>; Wed, 21 Nov 2018 08:56:44 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=fSAp1f/ZCbKqXXO8c9m1lwsRmSVPfInIJ91D9TdClnY=; b=MMLYohTMWukQUy3td9DsEtcIB3iY1EAih1V/F1OWnIeahj42o+ocbUo5uNyCrY1Kk7 1QJXH8JC2kUXK5X5dP083GFwN4X7MJMjtjuMSYOtetQ9TKS73vDVpGLHXYBzmVvR3EfO UADrry4ThrcBALwCc1VuhVUDlUX/YVN59hx8ZmdmvmlxkManQykA1eRDoPCoPWiWb8T5 SOTRizxSD6LC+VK3Cf22RnT+FebDKW9qIo8OvjWaWPhaS+m5gLWhMTa2awiC4n4IRItu cgR/wetDPZYZ7cp8c2nQDk6cyHan7wsppce4IWRWfS2kBfXXDY1PdHgPjW2BeauJRUwN XTBA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=fSAp1f/ZCbKqXXO8c9m1lwsRmSVPfInIJ91D9TdClnY=; b=Rw2Y9shfzV0bVxLvbZfsX8ig8msIWDys30BpbTIWC2rRISWKZF8np7Vb4OJpWdHkRH MobrsDro83jRfLP7piPxLbEuJuRsGjvvSLNUJrKrb+QTzqGegSdqvYvUeeiBh+HOIYcD W5DcfczzPoNkxQyy2khZ/CmjvUgGzHdolotirgVlc1XI8JY/QKq5kvSowmrx+EnFMtTj rZRUfGiIE1XgvR6QBnYE9JoudPY22qxEIOaddDr2eNhc+/pOLrmFMFn9nWnFdEDo1TVb YUyaPdmHxyVUsRbs7k4HHSRgeYAm3wlCS8jL2IAv8GwR/xdSXi4kImidfhY8GvUccM9p dktg==
X-Gm-Message-State: AA+aEWYuLsD/Y7QLWPPQ3eF/aLuiCjfsSrscrh6Fcm1U2lMtDu7ihWy4 y6nOE0M/xiX0lDlsuOVLEd/QEMwr
X-Google-Smtp-Source: AFSGD/U2Gj/QN60vvfVNoVBezkInm9aCKMGc9dn0DLtyDdaTJhXn7an1RvWrC20xi7JfGE9Lb/y4uA==
X-Received: by 2002:a17:902:d905:: with SMTP id c5mr7429320plz.43.1542819403465; Wed, 21 Nov 2018 08:56:43 -0800 (PST)
Received: from ?IPv6:2603:3024:151c:55f0:b846:7f86:7242:46cc? ([2603:3024:151c:55f0:b846:7f86:7242:46cc]) by smtp.gmail.com with ESMTPSA id 125sm720483pfx.159.2018.11.21.08.56.42 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 21 Nov 2018 08:56:42 -0800 (PST)
Content-Type: multipart/alternative; boundary="Apple-Mail-8BB5FE77-17FC-44F8-9399-D9D874721E00"
Mime-Version: 1.0 (1.0)
From: Dino Farinacci <farinacci@gmail.com>
X-Mailer: iPhone Mail (16B92)
In-Reply-To: <CAC8QAcf5AuVRJ3UgddLHOyXNnFU0CBFiqMOWHKEAc4tZn0mX0A@mail.gmail.com>
Date: Wed, 21 Nov 2018 08:56:42 -0800
Content-Transfer-Encoding: 7bit
Message-Id: <BADA8C6E-ED41-43A1-B529-5C7C922C1914@gmail.com>
References: <CO1PR15MB109589470678B3C515CC60D7D0C30@CO1PR15MB1095.namprd15.prod.outlook.com> <CAC8QAcf5AuVRJ3UgddLHOyXNnFU0CBFiqMOWHKEAc4tZn0mX0A@mail.gmail.com>
To: dmm@ietf.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmm/SilsZREqj_qaaXT01FzZOlzcrT4>
Subject: Re: [DMM] Call for adoption of draft-hmm-dmm-5g-uplane-analysis-02 as DMM WG document
X-BeenThere: dmm@ietf.org
X-Mailman-Version: 2.1.29
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, 21 Nov 2018 16:56:46 -0000

Note that I presented LISP to CT4 in August. They were kind enough to give me a slot without a WI being ready. 

They asked me to provide a proposal about how a IETF control-plane (specifically LISP) could be used to help manage the AMF, SMF, PCF, AUSF, and UDM functions. They were intrigue about using a different kind of control plane versus a Restful management plane that many of their “N interface” designs are based on. 

Maybe this WG should devote time to solving control plane issues in mobile networks. And I can say that the LISP WG would be enthusiastic to work with DMM. 

CT4 was not really interested in solving any data plane issues because they think many of the IETF proposals are no different, or not different enough from GTP. That was my interpretation. 

Cheers,
Dino

> On Nov 21, 2018, at 7:16 AM, Behcet Sarikaya <sarikaya2012@gmail.com> wrote:
> 
> 
> 
>> On Wed, Nov 14, 2018 at 3:53 PM David Allan I <david.i.allan@ericsson.com> wrote:
>> HI
>> 
>>  
>> 
>> AFAIK 3GPP CT4 is looking for work it can adopt, and has indicated that it wishes to perform the analysis itself. When they were directed to this document in the recent IETF DMM liaison, it  resulted in a liaison reply clearly indicated they would define their own criteria.
>> 
>> https://datatracker.ietf.org/liaison/1590/
>> 
>>  
>> 
>> However in the draft it states in the introduction: “However we believe that to provide adequate information for 3GPP, we need to clearly understand what the current user plane protocol is in Release 15, and architectural requirements for the user plane.” And in the conclusion “Our conclusion here is that we suggest the UP protocol study work in 3GPP takes into account the evaluation aspects described in Section 5.”, there is more, but I do not feel a need to be pedantic about it.
>> 
>>  
>> 
>> So the purpose of this draft seems to explicitly be to do work for 3GPP that they have explicitly said they DO NOT WANT.
>> 
>>  
>> 
>> At the same time I do not see anything in the charter that suggests we should be doing this work either.  It would appear to have little to do with DMM’s chartered direction.
>> 
>>  
>> 
>> As such I am opposed to adoption of the draft.
>> 
>>  
>> 
> 
> +1
> 
> I had raised similar issues before.
> 
> BTW no offense to Shunsuke.
> 
> and no offense to my friend Sri :-)
> 
> Behcet 
>> Cheers
>> 
>> Dave
>> 
>>  
>> 
>>  
>> 
>> _______________________________________________
>> dmm mailing list
>> dmm@ietf.org
>> https://www.ietf.org/mailman/listinfo/dmm
> _______________________________________________
> dmm mailing list
> dmm@ietf.org
> https://www.ietf.org/mailman/listinfo/dmm

v2.23.0 | Report a Bug | By Email