Re: [5gangip] blockchain mapping system

"FIGURELLE, TERRY F" <tf2934@att.com> Mon, 04 June 2018 22:09 UTC

Return-Path: <tf2934@att.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 6FBB0130E05 for <5gangip@ietfa.amsl.com>; Mon, 4 Jun 2018 15:09:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level:
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham 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 kqg-4mfeKMA0 for <5gangip@ietfa.amsl.com>; Mon, 4 Jun 2018 15:09:51 -0700 (PDT)
Received: from mx0a-00191d01.pphosted.com (mx0b-00191d01.pphosted.com [67.231.157.136]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3F6B4130E02 for <5gangip@ietf.org>; Mon, 4 Jun 2018 15:09:51 -0700 (PDT)
Received: from pps.filterd (m0049462.ppops.net [127.0.0.1]) by m0049462.ppops.net-00191d01. (8.16.0.22/8.16.0.22) with SMTP id w54IjorE002613; Mon, 4 Jun 2018 14:45:54 -0400
Received: from flpd657.enaf.ffdc.sbc.com (sbcsmtp9.sbc.com [144.160.128.153]) by m0049462.ppops.net-00191d01. with ESMTP id 2jd8wkumen-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Mon, 04 Jun 2018 14:45:51 -0400
Received: from enaf.ffdc.sbc.com (localhost [127.0.0.1]) by flpd657.enaf.ffdc.sbc.com (8.14.5/8.14.5) with ESMTP id w54Ije9i061607; Mon, 4 Jun 2018 11:45:40 -0700
Received: from zlp25945.vci.att.com (zlp25945.vci.att.com [135.213.92.139]) by flpd657.enaf.ffdc.sbc.com (8.14.5/8.14.5) with ESMTP id w54IjVhd061426; Mon, 4 Jun 2018 11:45:32 -0700
Received: from zlp25945.vci.att.com (zlp25945.vci.att.com [127.0.0.1]) by zlp25945.vci.att.com (Service) with ESMTP id 3E7C4410F454; Mon, 4 Jun 2018 18:45:31 +0000 (GMT)
Received: from CAFRFD1MSGHUBAG.ITServices.sbc.com (unknown [130.4.169.164]) by zlp25945.vci.att.com (Service) with ESMTPS id 1BD8C410F443; Mon, 4 Jun 2018 18:45:31 +0000 (GMT)
Received: from CAFRFD1MSGUSRJI.ITServices.sbc.com ([169.254.8.176]) by CAFRFD1MSGHUBAG.ITServices.sbc.com ([130.4.169.164]) with mapi id 14.03.0399.000; Mon, 4 Jun 2018 11:45:30 -0700
From: "FIGURELLE, TERRY F" <tf2934@att.com>
To: Dino Farinacci <farinacci@gmail.com>, =?utf-8?B?Sm9yZGkgUGFpbGxpc3PDqSBWaWxhbm92YQ==?= <jordip@ac.upc.edu>
CC: Mikael Abrahamsson <swmike@swm.pp.se>, "5gangip@ietf.org" <5gangip@ietf.org>, ".Austin 220" <austin220a@labs.att.com>
Thread-Topic: [5gangip] blockchain mapping system
Thread-Index: AQHTxUbFf78uRPb4CECiNt5n3A2vx6PkGoiAgGUBJYCAAWWwgIAARdEAgAX79cA=
Date: Mon, 4 Jun 2018 18:45:29 +0000
Message-ID: <1AFE10CF28AE8B4C9663445736B8034D382609D4@CAFRFD1MSGUSRJI.ITServices.sbc.com>
References: <c7f9f879-f656-2e26-319a-a61122205c7c@ac.upc.edu> <alpine.DEB.2.20.1803270849010.20609@uplift.swm.pp.se> <1AFE10CF28AE8B4C9663445736B8034D38255115@CAFRFD1MSGUSRJI.ITServices.sbc.com> <bd83d7cc-606e-16ad-7e3c-c4b33f57a63b@ac.upc.edu> <8E8DF836-B3BF-4E44-90D9-E953B2C60DB0@gmail.com>
In-Reply-To: <8E8DF836-B3BF-4E44-90D9-E953B2C60DB0@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [130.10.38.13]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2018-06-04_13:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_policy_notspam policy=outbound_policy score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1015 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1805220000 definitions=main-1806040216
Archived-At: <https://mailarchive.ietf.org/arch/msg/5gangip/PNKlInTkYOWgs_wiSMspy9kMPhU>
Subject: Re: [5gangip] blockchain mapping system
X-BeenThere: 5gangip@ietf.org
X-Mailman-Version: 2.1.26
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: Mon, 04 Jun 2018 22:09:54 -0000

I was responding to the estimate for the example given and comparing that to virtualized UPF/SPGW. Note that you can't partition prefix's without causing other issues. This was one of the challenges with learn with SDN.

> -----Original Message-----
> From: Dino Farinacci <farinacci@gmail.com>
> Sent: Thursday, May 31, 2018 7:47 AM
> To: Jordi Paillissé Vilanova <jordip@ac.upc.edu>
> Cc: FIGURELLE, TERRY F <tf2934@att.com>om>; Mikael Abrahamsson
> <swmike@swm.pp.se>se>; 5gangip@ietf.org
> Subject: Re: [5gangip] blockchain mapping system
> 
> Terry, let me expand what Jordi is trying to get across. The LISP-DDT structure
> is relatively static and the delegation of EID-prefixes is the hierarchical
> structure of the DDT-roots, the DDT-nodes that are children of the roots, and
> the map-servers that are DDT leaf nodes.
> 
> What authenticates which Map-Servers are allowed to accept Map-Registers
> for their delegated prefixes can be stored in the blockchain. This is a write to
> the blockchain which is unmuutablely verified at the time the DDT branch is
> provisioned.
> 
> When a Map-Resolver is processing a Map-Request from an ITR, and receives
> a Map-Referral from a Map-Server, it could look up the Map-Server in the
> blockchain to verify that the EID-prefix in the referral matches the EID-prefix
> in the transaction stored on the blockchain.
> 
> Also, the Map-Referral is signed by the Map-Server, so the Map-Resolver
> could verify the signature by obtaining the public-key from the blockchain or
> use the one the DDT parent of the Map-Server returned in the Map-Referral
> (as well as make some conclusions if they differ).
> 
> There is no push mechanism here and the Map-Resolver gets EID->Map-
> Server referral entries by using DDT on demand. Blockchain is used to
> validate the address allocations and delegations and not any map-cache
> entries, which would change much more frequently then these delegations.
> 
> Dino
> 
> > On May 31, 2018, at 3:36 AM, Jordi Paillissé Vilanova <jordip@ac.upc.edu>
> wrote:
> >
> > Hi Terry,
> >
> > I agree, but you can use it to store pointers to the servers storing the
> mappings (like a DNS for mappings). Then these servers can support fast and
> dynamic updates.
> >
> > Regards,
> >
> > Jordi
> >
> >
> > El 30/05/18 a les 22:21, FIGURELLE, TERRY F ha escrit:
> >> Plus how can it be fast enough and propagating mapping information to all
> servers that store mappings is a huge challenge on physically large networks.
> >>
> >>> -----Original Message-----
> >>> From: 5gangip <5gangip-bounces@ietf.org> On Behalf Of Mikael
> >>> Abrahamsson
> >>> Sent: Monday, March 26, 2018 11:50 PM
> >>> To: Jordi Paillissé Vilanova <jordip@ac.upc.edu>
> >>> Cc: 5gangip@ietf.org
> >>> Subject: Re: [5gangip] blockchain mapping system
> >>>
> >>> On Mon, 26 Mar 2018, Jordi Paillissé Vilanova wrote:
> >>>
> >>>> That said, depending on the dynamics of the mappings the blockchain
> >>>> is suitable or not for a mapping system. If mappings change
> >>>> frequently, it's not useful, so  it does not make sense for the 5G use-
> case.
> >>>>
> >>>> However, a blockchain can be useful to authenticate the servers
> >>>> that store such mappings, because this information changes way more
> >>>> slowly than mappings. A similar scenario is described in this draft:
> >>>> https://urldefense.proofpoint.com/v2/url?u=https-
> 3A__datatracker.ietf.
> >>>> org_doc_draft-2Dpaillisse-2Dsidrops-
> 2Dblockchain_&d=DwIDaQ&c=LFYZ-
> >>> o9_H
> >>>
> UMeMTSQicvjIg&r=tO_sNxa2NTxwl2paJIf4zw&m=gFRQ2s_dLZtBZOQpFDDiG
> >>> YKH8WUKw
> >>>
> _ZhBg4_uUdEFzo&s=UNs9FqOBStXgWINVb_jrtsjbdjKFsgkJiZmkt1O2YmY&e=
> >>>
> >>> "The main outcomes of the
> >>>     analysis are that blockchain is suitable in environments with
> >>>     multiple distrusting parties and that Proof of Stake is a potential
> >>>     candidate for a consensus algorithm."
> >>>
> >>> In what scenario for 5G is this applicable?
> >>>
> >>> --
> >>> Mikael Abrahamsson    email: swmike@swm.pp.se
> >> _______________________________________________
> >> 5gangip mailing list
> >> 5gangip@ietf.org
> >> https://urldefense.proofpoint.com/v2/url?u=https-
> 3A__www.ietf.org_mai
> >> lman_listinfo_5gangip&d=DwIFaQ&c=LFYZ-
> o9_HUMeMTSQicvjIg&r=tO_sNxa2NTx
> >>
> wl2paJIf4zw&m=7kFHRLEmRPFqBrQZoS0uskFEHRrJ6lOuxu4HoknmfEQ&s=Uo
> s3OVgr-
> >> -LjBXlv97ceLrZggf2lKyU_-TzwMCBZMY8&e=
> >
> > _______________________________________________
> > 5gangip mailing list
> > 5gangip@ietf.org
> > https://urldefense.proofpoint.com/v2/url?u=https-
> 3A__www.ietf.org_mail
> > man_listinfo_5gangip&d=DwIFaQ&c=LFYZ-
> o9_HUMeMTSQicvjIg&r=tO_sNxa2NTxwl
> >
> 2paJIf4zw&m=7kFHRLEmRPFqBrQZoS0uskFEHRrJ6lOuxu4HoknmfEQ&s=Uos3
> OVgr--Lj
> > BXlv97ceLrZggf2lKyU_-TzwMCBZMY8&e=