IETF Logo Mail Archive

Re: [lisp] Lisp Portable Edge Multipoint Sockets

Sharon Barkai <sharon.barkai@getnexar.com> Tue, 22 November 2022 14:57 UTC

Return-Path: <sharon.barkai@getnexar.com>
X-Original-To: lisp@ietfa.amsl.com
Delivered-To: lisp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D5F98C1522C5 for <lisp@ietfa.amsl.com>; Tue, 22 Nov 2022 06:57:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.095
X-Spam-Level:
X-Spam-Status: No, score=-7.095 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=getnexar.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xxspYxz4CVVd for <lisp@ietfa.amsl.com>; Tue, 22 Nov 2022 06:57:26 -0800 (PST)
Received: from mail-wr1-x42f.google.com (mail-wr1-x42f.google.com [IPv6:2a00:1450:4864:20::42f]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 36E24C14F73A for <lisp@ietf.org>; Tue, 22 Nov 2022 06:57:26 -0800 (PST)
Received: by mail-wr1-x42f.google.com with SMTP id z4so10515807wrr.3 for <lisp@ietf.org>; Tue, 22 Nov 2022 06:57:26 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=getnexar.com; s=google; h=to:references:message-id:cc:date:in-reply-to:from:subject :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=0NgqIlC9OhU4m+YW+uf65wwly/qYoQqX0v6ihSpaGSI=; b=Ifj4hIeuPcg26Vj8d+u2yFvyoyUwwy1fIvtDVBDZCNMxIuEi25lmgzqTRVA5+2cANV QYeGbB8U/S71Qdd8DSnV6F8DERGoork9xrU8az4FrsS9k/aAkWz9G0TXH/W+mhnbqTt9 VL/iziAJ/je4rSJSWbswcpje3gmRh8HeQlFfs=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=to:references:message-id:cc:date:in-reply-to:from:subject :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=0NgqIlC9OhU4m+YW+uf65wwly/qYoQqX0v6ihSpaGSI=; b=QUZ+urgBvu3Eh/D9Upz/xcBEpa4vUF7FZvAc7deqdRdJv10XeqNJQYqGmaB2vulOSS WdJmg4IyFPIv5cArMaxejidO8KZXVdGDbpowav9kJF3aPy8He/PpGBwfGsrccrYR++pH GoNIUrbdV3z2g3KYHWfm6mbfuwTY39znGMe9Em4BBfappDeLXTINRKnzC+p3aZo1sv40 me0IJsQiv1nphQ2K5de00ELoqXbA7F2B8SC3PEL/aJvik7R+kViA4wFUvZ8Qpx6MUlXL z7lMXkz4n9GiOUY7vqtx7Moh6a68+r12A9hUivwjhXMxodJb00NQ7ZCNGd8qD2cWFxgd a4Pw==
X-Gm-Message-State: ANoB5pm0NlRPdszqx2DnlNpfESepzFDeCo3QB1QvJBIJJ1sc9goS6l6L V2DkRZuCuWk1N/5pNE5S81c8d/kwHe7L/SpP
X-Google-Smtp-Source: AA0mqf6o+XbxGEhz8ugoxZIyuzuIyNznjiuM2jCZH//z0zNgzJleU2q25SMUZf4yeZWYrsO11nhIJQ==
X-Received: by 2002:a5d:4404:0:b0:236:657e:757e with SMTP id z4-20020a5d4404000000b00236657e757emr6665720wrq.350.1669129044237; Tue, 22 Nov 2022 06:57:24 -0800 (PST)
Received: from smtpclient.apple ([46.120.74.130]) by smtp.gmail.com with ESMTPSA id hg12-20020a05600c538c00b003cf7055c014sm17669631wmb.1.2022.11.22.06.57.23 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Tue, 22 Nov 2022 06:57:23 -0800 (PST)
Content-Type: multipart/alternative; boundary="Apple-Mail=_F96996FA-8E08-4248-93BC-1CD073F2225B"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3731.200.110.1.12\))
From: Sharon Barkai <sharon.barkai@getnexar.com>
In-Reply-To: <AE72F2C0-78ED-4564-81B9-4427C8A62149@gmail.com>
Date: Tue, 22 Nov 2022 16:57:11 +0200
Cc: "lisp@ietf.org list" <lisp@ietf.org>
Message-Id: <23C4FDF1-6FB6-4DE7-B281-B1B8C5FD0AC6@getnexar.com>
References: <10FAEDDA-8BFD-4D89-BD36-243BD4FE4F28@getnexar.com> <AE72F2C0-78ED-4564-81B9-4427C8A62149@gmail.com>
To: Dino Farinacci <farinacci@gmail.com>
X-Mailer: Apple Mail (2.3731.200.110.1.12)
Archived-At: <https://mailarchive.ietf.org/arch/msg/lisp/yx0iiKSqHX5hCYFYgLv0RqhRaHA>
Subject: Re: [lisp] Lisp Portable Edge Multipoint Sockets
X-BeenThere: lisp@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: List for the discussion of the Locator/ID Separation Protocol <lisp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/lisp>, <mailto:lisp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/lisp/>
List-Post: <mailto:lisp@ietf.org>
List-Help: <mailto:lisp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lisp>, <mailto:lisp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 22 Nov 2022 14:57:29 -0000

https://datatracker.ietf.org/doc/html/draft-barkai-lisp-pems

> On Nov 21, 2022, at 20:33, Dino Farinacci <farinacci@gmail.com> wrote:
> 
> Yes, everything you can define the better. Even a "socket" since its an overloaded term. Plus you want to define terms based on how the document is going to use them. So defining "EID" in the context of your document would make the ideas more clear. Like an EID in this spec defines an object versus a host.

Added 
> 
> I don't think there is a standard format for describing the API. Just calls and input and output parameter descriptions you should include.

Added QueueRead(EID, Frame) ChannelWrite(EID, EID, Frame)
> 
> As for eBPF, just describe what filters you are need to use to associate packet flows with an EID. And that this is a local matter and the flows are NOT put in the mapping system like it could be for the Multi-Tuple draft.

Queues receive: [[ Frame Packets ] Source EID, Socket EID] RTR RLOC, Current Host RLOC]
Channels send : [[ Frame Packets ] Socket EID, Theme EID] Current Host RLOC, RTR RLOC]

> 
> I am not sure who you are referring to but I know a lot of people that use eBPF. You should google for a list name and propose they review the document and definitely invite them to IETF.
> 

ok 

> Dino
> 
>>

v2.23.0 | Report a Bug | By Email