IETF Logo Mail Archive

Re: [Ideas] [5gangip] Mapping System Requirements and draft-padma-ideas-problem-statement-00.txt

Padmadevi Pillay Esnault <padma@huawei.com> Thu, 29 September 2016 22:32 UTC

Return-Path: <padma@huawei.com>
X-Original-To: ideas@ietfa.amsl.com
Delivered-To: ideas@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0795312B323 for <ideas@ietfa.amsl.com>; Thu, 29 Sep 2016 15:32:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.537
X-Spam-Level:
X-Spam-Status: No, score=-6.537 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-2.316, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
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 iEvhEt8vj8LK for <ideas@ietfa.amsl.com>; Thu, 29 Sep 2016 15:31:56 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C1F1712B32B for <ideas@ietf.org>; Thu, 29 Sep 2016 15:31:55 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml704-cah.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id CXD64464; Thu, 29 Sep 2016 22:25:31 +0000 (GMT)
Received: from SJCEML702-CHM.china.huawei.com (10.218.25.35) by lhreml704-cah.china.huawei.com (10.201.5.130) with Microsoft SMTP Server (TLS) id 14.3.235.1; Thu, 29 Sep 2016 23:25:30 +0100
Received: from SJCEML701-CHM.china.huawei.com ([169.254.3.53]) by SJCEML702-CHM.china.huawei.com ([169.254.4.207]) with mapi id 14.03.0235.001; Thu, 29 Sep 2016 15:25:20 -0700
From: Padmadevi Pillay Esnault <padma@huawei.com>
To: Rex Buddenberg <buddenbergr@gmail.com>, "ideas@ietf.org" <ideas@ietf.org>
Thread-Topic: [5gangip] Mapping System Requirements and draft-padma-ideas-problem-statement-00.txt
Thread-Index: AQHSGddmZXWSrtN+JkGtBik7W3lSAKCP874AgAD4HICAACvoAIAAGYSA///Y7mA=
Date: Thu, 29 Sep 2016 22:25:19 +0000
Message-ID: <EC7A99B9A59C1B4695037EEB5036666B90DEC7@SJCEML701-CHM.china.huawei.com>
References: <e78c8b96ec1949c0bc25924464f257ea@HE105831.emea1.cds.t-internal.com> <57EB89C1.8070805@uni-tuebingen.de> <7AE6A4247B044C4ABE0A5B6BF427F8E230A1152C@YYZEML702-CHM.china.huawei.com> <88EEBDA1-46A3-48D1-9851-64749837705D@gmail.com> <CAC8QAccTRJv5+0Z6rR92v_sbOzY2+0yrnYt8ybU-+nUKF-1KQg@mail.gmail.com> <F9A30FDA-4703-47BF-A0DF-6996BCF12B96@gmail.com> <CAD6AjGSNu3wy_Zxne7m0k3ZeoUdLXvWo6N+DyVJSEMT5w8sjbw@mail.gmail.com> <CAC8QAcdk-ScwScdYdoOVzbQ_pzw2cbTy0WGg+UW2kTqhHdvafQ@mail.gmail.com> <7AE6A4247B044C4ABE0A5B6BF427F8E230A1272B@YYZEML702-CHM.china.huawei.com> <CAC8QAcdDn++ruy3XXqx=mOMfMQckATOn7saJSwuTb1Z963RXZQ@mail.gmail.com> <1475170501.2311.528.camel@gmail.com>
In-Reply-To: <1475170501.2311.528.camel@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.109.109.251]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A020202.57ED94DC.0086, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0, ip=169.254.3.53, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: b96db9cb861e9be967deaa30c6fd0c8d
Archived-At: <https://mailarchive.ietf.org/arch/msg/ideas/g-gW4oWNDZHqSmTCWiMG_coxD8U>
Cc: Ca By <cb.list6@gmail.com>, "sarikaya@ieee.org" <sarikaya@ieee.org>, Michael Menth <menth@uni-tuebingen.de>, Dino Farinacci <farinacci@gmail.com>, AshwoodsmithPeter <Peter.AshwoodSmith@huawei.com>
Subject: Re: [Ideas] [5gangip] Mapping System Requirements and draft-padma-ideas-problem-statement-00.txt
X-BeenThere: ideas@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "Discussions relating to the development, clarification, and implementation of control-plane infrastructures and functionalities in ID enabled networks." <ideas.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ideas>, <mailto:ideas-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ideas/>
List-Post: <mailto:ideas@ietf.org>
List-Help: <mailto:ideas-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ideas>, <mailto:ideas-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Sep 2016 22:32:10 -0000

See below

-----Original Message-----
From: 5gangip [mailto:5gangip-bounces@ietf.org] On Behalf Of Rex Buddenberg
Sent: Thursday, September 29, 2016 10:35 AM
To: sarikaya@ieee.org; AshwoodsmithPeter
Cc: 5gangip@ietf.org; Ca By; Michael Menth; Dino Farinacci
Subject: Re: [5gangip] Mapping System Requirements and draft-padma-ideas-problem-statement-00.txt

On Thu, 2016-09-29 at 11:03 -0500, Behcet Sarikaya wrote:
> 
> In short, multicast mobility type of work is difficult to justify but
> certainly technically challenging :)

Not so (difficult to justify).
[Padma Pillay Esnault] 
Agree here. 

If you look at the nature of emergency services data, a great deal of
it is multicast in nature -- has to go >1 places.  Indeed if you talk
to EMS folks who's view of the world is Land Mobile Radio, they have a
different set of terminology, but it's multicast.

Yes, technically challenging relative to unicast.  But if you get the
multicast right, unicast is a simpler subset.

Belongs in scope.

[Padma Pillay Esnault] Agree. As we are moving towards a hyper-connected society, more and more services will multicast in nature. Do you really want to control/communicate to things as in internet of things one by one?

v2.8.7 | Report a Bug | By Email