[Ideas-discuss] New Non-WG Mailing List: ideas-discuss

IETF Secretariat <ietf-secretariat@ietf.org> Fri, 20 May 2022 20:29 UTC

Return-Path: <ietf-secretariat@ietf.org>
X-Original-To: ideas-discuss@ietf.org
Delivered-To: ideas-discuss@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 38ABDC1D5ACD; Fri, 20 May 2022 13:29:07 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: IETF Secretariat <ietf-secretariat@ietf.org>
To: IETF Announcement List <ietf-announce@ietf.org>
Cc: warren@kumari.net, rwilton@cisco.com, ideas-discuss@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 8.3.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: ietf@ietf.org
Message-ID: <165307854721.8009.12707327443684909050@ietfa.amsl.com>
Date: Fri, 20 May 2022 13:29:07 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ideas-discuss/jzHQZnp4PbQszW-WTGVyN7ilAMo>
Subject: [Ideas-discuss] New Non-WG Mailing List: ideas-discuss
X-BeenThere: ideas-discuss@ietf.org
X-Mailman-Version: 2.1.34
List-Id: Ideas-discuss <ideas-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ideas-discuss>, <mailto:ideas-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ideas-discuss/>
List-Post: <mailto:ideas-discuss@ietf.org>
List-Help: <mailto:ideas-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ideas-discuss>, <mailto:ideas-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 20 May 2022 20:29:07 -0000

A new IETF non-working group email list has been created.

List address: ideas-discuss@ietf.org
Archive: https://mailarchive.ietf.org/arch/browse/ideas-discuss/
To subscribe: https://www.ietf.org/mailman/listinfo/ideas-discuss

Purpose:
This list is a safe place to discuss new (IETF related)  *technical* ideas. It designed to be a place to float new ideas, like 'I've always wanted a protocol that allows me to signal my preferred flavor of coffee. It seems like I should be able to encode this in the source port of packets (e.g 2000-2999 is Americano, 3000-3999 is Espresso, etc), but I'm not really sure if this is a: something that other people also want, b: if the source port idea is a reasonable approach. What do people think?!
 

This list belongs to IETF area: OPS

For additional information, please contact the list administrators.