[lp-wan] draft-architecture-02-inputs New Session

Ana Minaburo <anaminaburo@gmail.com> Tue, 23 May 2023 16:40 UTC

Return-Path: <anaminaburo@gmail.com>
X-Original-To: lp-wan@ietfa.amsl.com
Delivered-To: lp-wan@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 44840C151541; Tue, 23 May 2023 09:40:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 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, HTML_MESSAGE=0.001, 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 m9UZ4c4CADyN; Tue, 23 May 2023 09:40:03 -0700 (PDT)
Received: from mail-qt1-x834.google.com (mail-qt1-x834.google.com [IPv6:2607:f8b0:4864:20::834]) (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 B6245C15171E; Tue, 23 May 2023 09:39:29 -0700 (PDT)
Received: by mail-qt1-x834.google.com with SMTP id d75a77b69052e-3f529239e4aso76293051cf.0; Tue, 23 May 2023 09:39:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1684859968; x=1687451968; h=cc:to:subject:message-id:date:from:reply-to:mime-version:from:to:cc :subject:date:message-id:reply-to; bh=Y4t2w/pchjRmfsAeZGedbWSEoAwaaClb1jCJynPY4Ts=; b=erS19QKtcTNPsVP/NrHSArKO9lByzCuaNBPtPzM5WdXxpYNqjgNHNBpUk9LafaXkdp m4uNABxE1G5sB5vMKH2jTEZU8psrdt8DAYwAc0cN3ZrWZpeAxAr0eX0r6fp34JPu6WpE DUvSAgghFTVfld2nxi9741oHKVNVIbIVsXdYxxLFJyP16F0uwJ+AFOchnP2ioO2dRuex r8tVQKhri+XlsS3xANfzzUGq4HALFP/8dTMqIJhafVG/KRIW2sWKfJ+TiupnUMcbqiLl l4ActgLD0VIXo+cW5RIsP0TImqzQKZJnA4wslh2GFY4iIksky/6YmzfNgu7Z+gzLI073 Lg7Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1684859968; x=1687451968; h=cc:to:subject:message-id:date:from:reply-to:mime-version :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=Y4t2w/pchjRmfsAeZGedbWSEoAwaaClb1jCJynPY4Ts=; b=CVj0ibQ2Xr+g0BLrt9Fg2koh+UGLMssBKauA1B1XAeqYCE+X6zbFgbcTVDJsoqCSTJ W/EdvisDMp3PxZa1f7YGAsHsNK99j2g79e6Z78FIRgAwyiXrDJfuV4ct6DbeH4M5tUOk 1XeAfRwwsj6TL7s+XKUlfs0sUlZlp33PgCTYV63uUej38U7cwazG98Hm+lP8QnuI6PAN FQcUTk/2O++Jt3rEN6rebJbmUk8YYMxnCb9eDR/72JUwddExloWiemggdQ27jF5kWkXE CV3AfygStX/K4nATdpNnCN4BPvq0eUeFT3B2Gu8GCmncSj3uo3VsD2+ORzVuRGpyvxty kXRA==
X-Gm-Message-State: AC+VfDyOxzwoBYNqEj2WJuqLZQYHPhSWazEjjtY+l7FKoJkGwN0eEPci nlCho5Y9z4GN+X4IViCcJoX9/JJNFNffNrSU/HSlYC2DKSDs5g==
X-Google-Smtp-Source: ACHHUZ6ehpqohV8/9pGysMFdV0kI+ZqXIjsACcawgW5MRrrACtGuBBdk5Gp/pcu++C9qRgGS1z5vgyWYVs8SXx8NVxs=
X-Received: by 2002:a05:622a:646:b0:3f6:bd82:c01b with SMTP id a6-20020a05622a064600b003f6bd82c01bmr2196930qtb.14.1684859968391; Tue, 23 May 2023 09:39:28 -0700 (PDT)
MIME-Version: 1.0
Reply-To: anaminaburo@gmail.com
From: Ana Minaburo <anaminaburo@gmail.com>
Date: Tue, 23 May 2023 18:39:17 +0200
Message-ID: <CAOPRf-fN-+H94YNnR+ud8m3Z5Y_NvY3DFw8hy4+S8jfXsTeCGw@mail.gmail.com>
To: "Pascal Thubert (pthubert)" <pthubert@cisco.com>
Cc: lp-wan <lp-wan@ietf.org>, schc@ietf.org
Content-Type: multipart/alternative; boundary="000000000000e98eed05fc5f071a"
Archived-At: <https://mailarchive.ietf.org/arch/msg/lp-wan/9fZw1RMQTIo1tkMz_qAXFSQCxhk>
Subject: [lp-wan] draft-architecture-02-inputs New Session
X-BeenThere: lp-wan@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "Low-Power Wide Area Networking \(LP-WAN\), also known as LPWA or Low-Rate WAN \(LR-WAN\)" <lp-wan.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/lp-wan>, <mailto:lp-wan-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/lp-wan/>
List-Post: <mailto:lp-wan@ietf.org>
List-Help: <mailto:lp-wan-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lp-wan>, <mailto:lp-wan-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 May 2023 16:40:04 -0000

Hello Pascal

   - 6. Section 5.3, the first paragraph, "rules cannot be modified during
   the session."
   - I agree with this point defined for the LPWAN applications and star
   topology, but how about other topologies like E2E and mesh and other
   applications like video on demand, audio, or web browsing? The Rules may
   not be fixed during a session, and the context needs to be updated in the
   same session.



Another good thread to have. How this is done would be left to be defined.
E.g., exactly when do the new rules apply? It seems safer/simpler to
negotiate a new "context" and start a new session with that new context.


[Ana] Starting a new session each time a new context is used seems very
heavy.

Especially if each time we need to make AAA security procedures.

For example, How many sessions a TCP connection will use? Is it possible to
keep the SCHC session open as long as the TCP connection or an RTP session
is alive, even if the Context change?