[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"doc-seo-513375-105":3,"detail-sidebar-cat-0-en-105":81,"doc-detail-513375-en":130},{"code":4,"msg":5,"data":6},0,"ok",{"site_id":7,"language":8,"slug":9,"title":10,"keywords":11,"description":12,"schema_data":13,"social_meta":74,"head_meta":76,"extra_data":78,"updated_unix":80},105,"en","lisp-data-plane-confidentiality-draft-farinacci-lisp-crypto-01-lisp-working-group","LISP Data-Plane Confidentiality draft-farinacci-lisp-crypto-01 - LISP Working Group","","Confidentiality draft notes the LISP data-plane design proposed by Dino Farinacci within the LISP Working Group, including a chronology of presentations and implementation work from 2013–2014 across IETF venues. It outlines a key exchange using Diffie-Hellman via Map-Request/Map-Reply, emphasizing that third parties do not store keys and that keys are ephemeral. Detailed packet-level steps describe ITR encapsulation, ETR decapsulation, shared-key computation, encryption/decapsulation, and cache updates, plus proposed changes labeled for version -01.",{"@graph":14,"@context":73},[15,34,56],{"@type":16,"itemListElement":17},"BreadcrumbList",[18,23,27,31],{"item":19,"name":20,"@type":21,"position":22},"https://docshare.wps.com","Home","ListItem",1,{"item":24,"name":25,"@type":21,"position":26},"https://docshare.wps.com/document/","Document",2,{"item":28,"name":29,"@type":21,"position":30},"https://docshare.wps.com/document/research-report/","Research & Report",3,{"item":32,"name":10,"@type":21,"position":33},"https://docshare.wps.com/document/lisp-data-plane-confidentiality-draft-farinacci-lisp-crypto-01-lisp-working-group/513375/",4,{"url":32,"name":10,"@type":35,"image":36,"author":41,"headline":10,"publisher":44,"fileFormat":47,"inLanguage":8,"description":12,"dateModified":48,"datePublished":49,"encodingFormat":47,"isAccessibleForFree":50,"interactionStatistic":51},"DigitalDocument",{"url":37,"@type":38,"width":39,"height":40},"https://docshare.wps.com/thumbnails/lisp-data-plane-confidentiality-draft-farinacci-lisp-crypto-01-lisp-working-group/513375.png","ImageObject",300,407,{"name":42,"@type":43},"pixelkiddo","Person",{"url":19,"name":45,"@type":46},"DocShare","Organization","application/pdf","2026-11-20","2026-10-06",true,{"@type":52,"interactionType":53,"userInteractionCount":55},"InteractionCounter",{"@type":54},"ViewAction",7,{"@type":57,"mainEntity":58},"FAQPage",[59,65,69],{"name":60,"@type":61,"acceptedAnswer":62},"What confidentiality mechanism does the draft describe for the LISP data plane?","Question",{"text":63,"@type":64},"It describes Diffie-Hellman key exchange using Map-Request/Map-Reply, followed by ITR encapsulation and ETR decapsulation with encryption based on a shared key. The draft emphasizes ephemeral keys and avoiding third-party key storage.","Answer",{"name":66,"@type":61,"acceptedAnswer":67},"How does the draft handle key exchange during Map-Request/Map-Reply?",{"text":68,"@type":64},"It performs an exchange to obtain local and remote keys, computes a shared key, and adds the corresponding EID-to-RLOC mapping into the map-cache. Subsequent packets are encrypted with the shared key before being sent and decrypted on receipt.",{"name":70,"@type":61,"acceptedAnswer":71},"What changes are indicated for version -01, and what is the working group status?",{"text":72,"@type":64},"The document includes a section titled “Changes to-01” and notes that there was no consensus in London about making this a WG document. It also states a request to make it a WG document at the current time.","https://schema.org",{"og:url":32,"og:type":75,"og:title":10,"og:site_name":45,"og:description":12},"article",{"robots":77,"canonical":32},"index,follow",{"doc_id":79,"site_id":7},513375,1791377568,{"code":4,"msg":82,"data":83},"success",[84,88,92,96,101,106,110,114,119,122,126],{"id":22,"doc_module":4,"doc_module_name":25,"category_name":85,"show_sort_weight":86,"slug":87},"Story & Novel",90,"story-novel",{"id":26,"doc_module":4,"doc_module_name":25,"category_name":89,"show_sort_weight":90,"slug":91},"Literature",80,"literature",{"id":33,"doc_module":4,"doc_module_name":25,"category_name":93,"show_sort_weight":94,"slug":95},"Exam",70,"exam",{"id":97,"doc_module":4,"doc_module_name":25,"category_name":98,"show_sort_weight":99,"slug":100},5,"Comic",60,"comic",{"id":102,"doc_module":4,"doc_module_name":25,"category_name":103,"show_sort_weight":104,"slug":105},6,"Technology",50,"technology",{"id":55,"doc_module":4,"doc_module_name":25,"category_name":107,"show_sort_weight":108,"slug":109},"Healthcare",40,"healthcare",{"id":111,"doc_module":4,"doc_module_name":25,"category_name":29,"show_sort_weight":112,"slug":113},8,30,"research-report",{"id":115,"doc_module":4,"doc_module_name":25,"category_name":116,"show_sort_weight":117,"slug":118},9,"Religion & Spirituality",20,"religion-spirituality",{"id":117,"doc_module":4,"doc_module_name":25,"category_name":120,"show_sort_weight":117,"slug":121},"World Cup","world-cup",{"id":123,"doc_module":4,"doc_module_name":25,"category_name":124,"show_sort_weight":123,"slug":125},10,"Lifestyle","lifestyle",{"id":127,"doc_module":4,"doc_module_name":25,"category_name":128,"show_sort_weight":97,"slug":129},19,"General","general",{"code":4,"msg":82,"data":131},{"doc_id":79,"user_id":132,"nickname":42,"user_avatar":133,"doc_module":4,"category_id":111,"category_name":29,"doc_title":10,"doc_description":12,"doc_content":134,"file_id":135,"file_url":136,"file_type":137,"file_size":138,"view_count":55,"is_deleted":4,"is_public":22,"is_downloadable":22,"audit_status":22,"page_count":55,"language":139,"language_code":8,"site_id":7,"html_lang":8,"table_of_contents":140,"faqs":141,"seo_title":142,"seo_description":12,"update_tm":143,"read_time":144,"preview_page_count":33,"preview_urls":145},962090883892,"https://ap-avatar.wpscdn.com/avatar/e00115db34f3e0f11b?x-image-process=image/resize,m_fixed,w_180,h_180&k=1790152879550218658","LISP Data-Plane Confidentiality draft-farinacci-lisp-crypto-01  \nLISP Working Group  \nToronto IETF-July 2014  \nHonolulu IETF-November 2014  \nDino Farinacci  \nChronology  \n• Presented ideas in LISP WG in Vancouver fall 2013  \n• Seek advice from SAAG in Vancouver fall 2013  \n• Present-00 draft in London spring 2014  \n• Wrote-00 implementation spring 2014  \n• Present-01 and implementation here in Toronto summer 2014  \nDesign Overview  \n• Diffie-Hellman exchange via Map-Request/Map-Reply  \n• Keys not stored by third-party  \n• Keys are ephemeral  \n• ITR encrypt-n-encap-> ETR decap-n-decrypt  \n• Rekeying part of RLOC-probing  \nKey Exchange  \n11:17:09 . 865: itr: Receive any/eth0 [0]22 .0 .0 .2 -> [0]33 .0 .0 .3, inner tos/ttl: 0/64, length: 84, packet: 45000054 00004000 400103a5 16000002 21000003 0800f9ec 1c4e0001 24b6ca53 00b70700 08090a0b 0c0d0e0f 10111213 14151617 18191a1b 1c1d1e1f ...  \n11:17:09 . 865: itr: Lookup for EID [0]33 .0 .0 .3 not found in map-cache  \n11:17:09 . 866: itr: Map-Request -> flags: adrspimxd, itr-rloc-count: 1 (+1), record-count: 1, nonce: 0x4989b9206a677ba3, source-eid: afi 1, [0]22 .0 .0 .2, target-eid: afi 1, [0]33 .0 .0 .3/32, ITR-RLOCs:  \n11:17:09 . 866: itr: itr-rloc: afi 1 [0]1 .0 .0 .2, g/p/local-key/remote-key: 2/7919/7129/none  \n11:17:09 . 866: itr: itr-rloc: afi 2 [0]2602:306:3a29:6c70:5cff:afe3:109d:173a  \n11:17:09 . 866: itr: ECM -> flags: sdem, inner IP: [0]1 .0 .0 .2 -> [0]33 .0 .0 .3, inner UDP: 39107 -> 4342  \n11:17:09 . 866: itr: Send Encapsulated-Control-Message to [1.0.0.5](1.0.0.5)  \n11:17:09 . 910: itr: Receive 90 bytes from [1.0.0.3](1.0.0.3) 4342, packet: 20000001 a37b676a 20b98949 000005a0 01081000  \n00000001 21000000 0000ff00 00054003 00000100 00300001 01000003 40030000 0b000022 01000000 00160400 00000208 00001eef 00000000 cb090000 00000000 00010100 0003  \n11:17:09 . 910: itr: Map-Reply -> flags: res, record-count: 1, nonce: 0x4989b9206a677ba3  \n11:17:09 . 910: itr: EID-record -> record-ttl: 1440, rloc-count: 1, action: no-action, auth, map-version: 0, afi:  \n1, [iid]eid/ml: [0]33 .0 .0 .0/8  \n11:17:09 . 954: itr: RLOC-record -> flags: LpR, 0/0/255/0, afi: 1, rloc: 1 .0 .0 .3, g/p/local-key/remote-key: 2/7919/7129/2507  \n11:17:09 . 954: itr: Compute shared-key with g/p/local-key/remote-key: 2/7919/7129/2507  \n11:17:09 . 954: itr: Add [0]33 .0 .0 .0/8 to map-cache with 1 RLOCs  \nE-n-E then D-n-D  \n11:17:10 .507: itr: Receive any/eth0 [0]22 .0 .0 .2 -> [0]33 .0 .0 .3, inner tos/ttl: 0/64, length: 84, packet: 45000054 00004000 400103a5 16000002 21000003 0800afe5 1c4e0003 26b6ca53 48bc0700 08090a0b 0c0d0e0f 10111213 14151617 18191a1b 1c1d1e1f ...  \n11:17:10 .511: itr: Lookup for EID [0]33 .0 .0 .3 found map-cache entry [0]33 .0 .0 .0/8  \n11:17:10 .512: itr: Packet hash is 0, best-rloc-list: [['1 .0 .0 .3', 'up-state']]  \n11:17:10 .512: itr: Encrypt with shared-key for key-id: 1, g/p/local-key/remote-key: 2/7919/7129/2507, rloc: [1.0.0.3](1.0.0.3)  \n11:17:10 .512: itr: Send LISP packet, outer RLOCs: [0]1 .0 .0 .2 -> [0]1 .0 .0 .3, outer tos/ttl: 0/63, outer UDP: 61925 -> 4341, inner EIDs: [0]22 .0 .0 .2 -> [0]33 .0 .0 .3, inner tos/ttl: 0/63, length: 132, encrypt/encap LISP-header -> flags: NlevipK1 , nonce: 0x4fb658, iid/lsb: 0x0, packet: 45000084 dfdf0000 3f119985 01000002 01000003 f1e510f5  \n00700000 814fb658 00000000 b89f2416 fadc4686 bab9f63c bfb0dc55 39d4911d ...  \n11:17:19 .574: etr: Receive LISP packet, outer RLOCs: [0]1 .0 .0 .2 -> [0]1 .0 .0 .3, outer tos/ttl: 0/63, outer UDP: 63335 -> 4341, inner EIDs: [0]22 .0 .0 .2 -> [0]33 .0 .0 .3, inner tos/ttl: 0/63, length: 120, decap/decrypt LISP-header-> flags: NlevipK1 , nonce: 0x4fb658, iid/lsb: 0x0, packet: 45000084 dfdf0000 3f119985 01000002 01000003 f76710f5  \n00700000 814fb658 00000000 45000054 00004000 3f0104a5 16000002 21000003 ...  \n11:17:20 .574: etr: Decrypt with shared-key for key-id: 1, g/p/local-key/remote-key: 2/7919/2507/7129, rloc: [1.0.0.2](1.0.0.2)  \n11:17:19 .580: etr: Forward packet for EIDs [0]22 .0 .0 .2 -> [0]","cbCaik8A6nZjsurw","https://ap.wps.com/l/cbCaik8A6nZjsurw","pdf",491413,"English","# Chronology\n# Design Overview\n# Key Exchange\n# Changes to-01\n## Working Group Work Item?","[{\"question\":\"What confidentiality mechanism does the draft describe for the LISP data plane?\",\"answer\":\"It describes Diffie-Hellman key exchange using Map-Request/Map-Reply, followed by ITR encapsulation and ETR decapsulation with encryption based on a shared key. The draft emphasizes ephemeral keys and avoiding third-party key storage.\"},{\"question\":\"How does the draft handle key exchange during Map-Request/Map-Reply?\",\"answer\":\"It performs an exchange to obtain local and remote keys, computes a shared key, and adds the corresponding EID-to-RLOC mapping into the map-cache. Subsequent packets are encrypted with the shared key before being sent and decrypted on receipt.\"},{\"question\":\"What changes are indicated for version -01, and what is the working group status?\",\"answer\":\"The document includes a section titled “Changes to-01” and notes that there was no consensus in London about making this a WG document. It also states a request to make it a WG document at the current time.\"}]","LISP Data-Plane Confidentiality draft-farinacci-lisp-crypto-01 - LISP Working Group | PDF",1791283920,18,[146,150,153,157],{"page_no":22,"url":147,"width":148,"height":149},"https://res-academy.cache.wpscdn.com/upload/kdocshare/2026-11-17/f8d51da7e28b9688e0c37568f37174cf.webp",983,736,{"page_no":26,"url":151,"width":152,"height":149},"https://res-academy.cache.wpscdn.com/upload/kdocshare/2026-11-17/94952a968f02ad60696c6eaf726393ff.webp",982,{"page_no":30,"url":154,"width":155,"height":156},"https://res-academy.cache.wpscdn.com/upload/kdocshare/2026-11-17/677416f332dfe12223a1b38f0812e86c.webp",981,735,{"page_no":33,"url":158,"width":159,"height":160},"https://res-academy.cache.wpscdn.com/upload/kdocshare/2026-11-17/438d50f3cc26f3e26a8dde3b363052f7.webp",980,734]