IETF Logo Mail Archive

[tsvwg] Fwd: New Version Notification for draft-reddy-tsvwg-explcit-signal-00.txt

tirumal reddy <kondtir@gmail.com> Fri, 10 February 2023 05:31 UTC

Return-Path: <kondtir@gmail.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DC910C16950E for <tsvwg@ietfa.amsl.com>; Thu, 9 Feb 2023 21:31:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.095
X-Spam-Level:
X-Spam-Status: No, score=-2.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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-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 (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 nuXaHkGRPsw2 for <tsvwg@ietfa.amsl.com>; Thu, 9 Feb 2023 21:31:36 -0800 (PST)
Received: from mail-lf1-x135.google.com (mail-lf1-x135.google.com [IPv6:2a00:1450:4864:20::135]) (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 998CAC16950D for <tsvwg@ietf.org>; Thu, 9 Feb 2023 21:31:36 -0800 (PST)
Received: by mail-lf1-x135.google.com with SMTP id o20so6632967lfk.5 for <tsvwg@ietf.org>; Thu, 09 Feb 2023 21:31:36 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :from:to:cc:subject:date:message-id:reply-to; bh=9UkMDvdDEUXXdMvyD+QnITo8os6x9FrqQVkbBlzG4Qs=; b=Ey6f9PuM+g4C1elW7NrIphm4cSTzWGCg6RzcwlvTnSyxf0bDpfvdH2CReIpbcDNdqk GvhxFV4tTAXUPG1QdkH7iBxv+Fm2poCI1oSSVfPdFyegdvIbIFWUZhJ6AY5uRQcCPMvR 7FjBSWtb0b6YptRMyVB/uVYTeb74LxhPaeGrM+Umt+gU1+o9gzbArPDzLSnloGKf15g8 RP9v11gqohCUQ6w0FewC1uZ/jQHSe6OCR+OIAQMzq4tiUGx2dQOgK1O/ZekFjuRefNp/ hk7tSJg/fu5HRUWcbLY+Mz2M5MjCWClbekUABknq6wJlabM1Zcdznz278djZmGET9r3A VK2w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=9UkMDvdDEUXXdMvyD+QnITo8os6x9FrqQVkbBlzG4Qs=; b=0E02UwLMkzfv3iS+0ED/C/h61MQ8V8636Qv3o/5Di8sq6ExWATb2tPJ2Bk6wnyFt5e PBiys8A2VLoWruDIejFGWso1JxNE5oX1YO79KKrRDfXLbScWH1v/6J9oMlOWwj0Wb5HH /alC/ZmxUZUNubBdnZBl+EHzbVhoH1oVb1nVgwMC4xYcdwKZbzysuWc70moJvEVYDj/b quz8UHQ1MVGQvnjNSHwkdRceEidVwDOt6Hd9CknM10lGoQQEiu23uXWAsDXOxxh/RRQG l6htg3z1L/3GYhHaaHRUHcoeMPmn9Cuar6M97J2HtMIRQMLbK3MFxeksbjuUPIdBIL3r vVCQ==
X-Gm-Message-State: AO0yUKVL4/3Ak45F+CWkMV8MG/+C1SsYxfvBBM8fCnlQEJl/HexSSEhA nDlUq9fE/lOIMMyx3UxwpwX3PuhuowAIazsZWv5MrMufsT0=
X-Google-Smtp-Source: AK7set+ffJFdKoSxUu4kBQaBGPwqEgnGrUk808RSeMiXYvvxPCLubtwN9HQkicZcJB2Pj97ZtVT7wS96x6dmGf1BEfo=
X-Received: by 2002:ac2:51c7:0:b0:4d5:86a8:55d1 with SMTP id u7-20020ac251c7000000b004d586a855d1mr2373174lfm.155.1676007093972; Thu, 09 Feb 2023 21:31:33 -0800 (PST)
MIME-Version: 1.0
References: <167592939329.52949.17763475463632062767@ietfa.amsl.com>
In-Reply-To: <167592939329.52949.17763475463632062767@ietfa.amsl.com>
From: tirumal reddy <kondtir@gmail.com>
Date: Fri, 10 Feb 2023 11:01:22 +0530
Message-ID: <CAFpG3gdFojRowTpo-DBDh2czC9d-KemSetmeaOC3VZ=COqvOgg@mail.gmail.com>
To: tsvwg@ietf.org
Content-Type: multipart/alternative; boundary="0000000000007a346805f451cf61"
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/osq_cj_ThHi6qN01GNcw-pL9mYQ>
Subject: [tsvwg] Fwd: New Version Notification for draft-reddy-tsvwg-explcit-signal-00.txt
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Feb 2023 05:31:38 -0000

Hi all,

The new draft
https://datatracker.ietf.org/doc/html/draft-reddy-tsvwg-explcit-signal
defines a mechanism for an endpoint to explicitly signal encrypted metadata
to the network, and the network to signal its ability to accommodate that
metadata back to the endpoint. This mechanism can be used where the
endpoints desire that network elements along the path receive these
explicit signals. It proposes three mechanisms to encrypt or obfuscate the
metadata in the explicit signal.

Comments and suggestions are welcome.

Cheers,
-Tiru

---------- Forwarded message ---------
From: <internet-drafts@ietf.org>
Date: Thu, 9 Feb 2023 at 13:26
Subject: New Version Notification for
draft-reddy-tsvwg-explcit-signal-00.txt
To: Tirumaleswar Reddy.K <kondtir@gmail.com>, Dan Wing <danwing@gmail.com>,
Mohamed Boucadair <mohamed.boucadair@orange.com>



A new version of I-D, draft-reddy-tsvwg-explcit-signal-00.txt
has been successfully submitted by Tirumaleswar Reddy and posted to the
IETF repository.

Name:           draft-reddy-tsvwg-explcit-signal
Revision:       00
Title:          Encrypted Transport Protocol Path Explicit Signals
Document date:  2023-02-08
Group:          Individual Submission
Pages:          18
URL:
https://www.ietf.org/archive/id/draft-reddy-tsvwg-explcit-signal-00.txt
Status:
https://datatracker.ietf.org/doc/draft-reddy-tsvwg-explcit-signal/
Htmlized:
https://datatracker.ietf.org/doc/html/draft-reddy-tsvwg-explcit-signal


Abstract:
   This document defines a mechanism for an endpoint to explicitly
   signal encrypted metadata to the network, and the network to signal
   its ability to accommodate that metadata back to the endpoint.  This
   mechanism can be used where the endpoints desire that network
   elements along the path receive these explicit signals.




The IETF Secretariat

v2.23.0 | Report a Bug | By Email