IETF Logo Mail Archive

Re: [Idr] Proposed CAN WG charter for discussion

Dino Farinacci <farinacci@gmail.com> Fri, 27 January 2023 22:54 UTC

Return-Path: <farinacci@gmail.com>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D3B10C14CE40; Fri, 27 Jan 2023 14:54:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.098
X-Spam-Level:
X-Spam-Status: No, score=-7.098 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, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, 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 ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Zouf3x2Ztlxu; Fri, 27 Jan 2023 14:54:34 -0800 (PST)
Received: from mail-pg1-x52a.google.com (mail-pg1-x52a.google.com [IPv6:2607:f8b0:4864:20::52a]) (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 25212C14CE33; Fri, 27 Jan 2023 14:54:34 -0800 (PST)
Received: by mail-pg1-x52a.google.com with SMTP id 7so4159550pga.1; Fri, 27 Jan 2023 14:54:34 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=to:references:message-id:content-transfer-encoding:cc:date :in-reply-to:from:subject:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=XhEhMjSCFdL6S1DtzyFFNnNFnp2s2iY3ENIpzgm04x8=; b=G2NSp9AJbRDkaz3r6twEFd7Yc3pkF4KGp0Ygig5yT9tfob/kBqEl5zX6YB7yutH9YK rlB7i5PHM4xaGCYNuhDhLGZjSyCOb6amkXbMdfn66i23wwhhUVNoyFZLOwECopZrBGpK 8/+gHtyXjCsKGvvU9kQvixrBCHJpYtxztaPZGa9k1ZGC6/7HsYUuY1UvjMHgfYxOLhBO 9M/m2+SKvQLG6tJU9DUNHvSdyC6KmN/Xf3geyjsy8vdqJIj2ar0OeCCYDeAnE/dMXIj4 Hl35X1TJl1DV52Yjg5FLKa04HItXbzWWSdnsvH5oPqjfhz4RE1UfZJMdELaDxATGnMGx sTVw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=to:references:message-id:content-transfer-encoding:cc:date :in-reply-to:from:subject:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=XhEhMjSCFdL6S1DtzyFFNnNFnp2s2iY3ENIpzgm04x8=; b=s0Dmzlw01stniXCgvawolLYofuV2UYH0T3ewyJTB3z/yvmlyb/03dSi4hj+t2Yc55C XFI0iV0HRjOvq3sUM8lr0vtSpx7tE6QsMw3Hj8DSnbit2aWhXp0oIED8uAdKpUi2AHv4 BOcXIOne7KFaLi1TaOtk3ikQn31TMGYg/8IbJG06QaaIoGF5cb9Bqs8iabg7fm+6C4G5 w6IIXpQFEozwHXN8j4taDU3pZxjxQl+hHL0MxcgmsR0MRDFx+0zi0leaj1ZwwxYKy8rF yBp9AIEJ0VjZ99sDqHeXJlQzC7js8EfMkdii9HhlunxcKJxJDcUfIj85HO/VjZG7h2+a xMcg==
X-Gm-Message-State: AO0yUKWUPGBe6oyaHoN5Kl2T6/YemIwd2g5xOOoDQpYladGKxtHs6aNa sSJmxi/8ixX++O775pQUmhA=
X-Google-Smtp-Source: AK7set+w5Aa7m/j2AMz9A4Pl/Ww/CJtHlJGVDj/cHfp12Fd/3shH3a3cgih68BE5TkCDQPszd19OYw==
X-Received: by 2002:a62:d459:0:b0:592:de72:4750 with SMTP id u25-20020a62d459000000b00592de724750mr2971880pfl.23.1674860073499; Fri, 27 Jan 2023 14:54:33 -0800 (PST)
Received: from smtpclient.apple (c-98-234-33-188.hsd1.ca.comcast.net. [98.234.33.188]) by smtp.gmail.com with ESMTPSA id q22-20020aa79836000000b00575caf80d08sm3151394pfl.31.2023.01.27.14.54.32 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Fri, 27 Jan 2023 14:54:33 -0800 (PST)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.120.41.1.1\))
From: Dino Farinacci <farinacci@gmail.com>
In-Reply-To: <CAOj+MMFNeq=rs8rmoBLCYVQgpMv4W5m7CCneCH5QFa+X=41egQ@mail.gmail.com>
Date: Fri, 27 Jan 2023 14:54:32 -0800
Cc: Linda Dunbar <linda.dunbar@futurewei.com>, John Scudder <jgs@juniper.net>, "can@ietf.org" <can@ietf.org>, "idr@ietf.org" <idr@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <3153333F-617D-4ED6-BE70-A29DB298BD73@gmail.com>
References: <53B67919-AD61-489D-8115-EBCB5CCE1976@juniper.net> <CO1PR13MB49207D831961BE1891CEEEF985CE9@CO1PR13MB4920.namprd13.prod.outlook.com> <70C0E859-8EDE-441E-A1F2-7FFA68B9B6D8@juniper.net> <CO1PR13MB4920B520CB00D82B0576F8E385CC9@CO1PR13MB4920.namprd13.prod.outlook.com> <CAOj+MMGdWbvm9t0GOpdWqmS5h4OMdmnX5_2kbU4ukkU6BXTnZQ@mail.gmail.com> <CO1PR13MB49205F1D5CE4D2EF99BAEFE985CC9@CO1PR13MB4920.namprd13.prod.outlook.com> <CAOj+MMFNeq=rs8rmoBLCYVQgpMv4W5m7CCneCH5QFa+X=41egQ@mail.gmail.com>
To: Robert Raszuk <robert@raszuk.net>
X-Mailer: Apple Mail (2.3696.120.41.1.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/2cnkLj-vnbb45xvHZyMBOJ750sQ>
Subject: Re: [Idr] Proposed CAN WG charter for discussion
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idr/>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 27 Jan 2023 22:54:35 -0000

> I know LISP roots started at the assumption that xTRs should be placed in routers vs ILNP idea (or family of ideas) to make it in the host - however today I think that even for LISP xTR can be natively implemented in the compute nodes itself. 

In the LISP deployments I'm involved with this is exactly where xTRs are deployed. And usually close-to/co-located to where the applications run. That means either in the same OS as the app or a VM/container to fault isolate the app from the  overlay.

Dino

v2.23.0 | Report a Bug | By Email