Re: [dispatch] IETF 117 - do you have something for DISPATCH?

Jim Fenton <fenton@bluepopcorn.net> Fri, 07 July 2023 16:50 UTC

Return-Path: <fenton@bluepopcorn.net>
X-Original-To: dispatch@ietfa.amsl.com
Delivered-To: dispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AE901C15171E; Fri, 7 Jul 2023 09:50:44 -0700 (PDT)
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=bluepopcorn.net
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 IoHXLocz10dR; Fri, 7 Jul 2023 09:50:39 -0700 (PDT)
Received: from v2.bluepopcorn.net (v2.bluepopcorn.net [IPv6:2607:f2f8:a994::2]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 55A4EC151710; Fri, 7 Jul 2023 09:50:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=bluepopcorn.net; s=supersize; h=Content-Transfer-Encoding:Content-Type: MIME-Version:References:In-Reply-To:Message-ID:Date:Subject:Cc:To:From:Sender :Reply-To:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help: List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=2YGPSD+PpZ1yDfujjoFwyLfqCUS9dKy9hi8RpLhkKx0=; b=k8Fa9zga98/4rvLUfyISM2cyR2 ghSKQ9aaJa6HGCjs9lRu4x3FZ9d9R+E6vMBEDVDqVZlGu9zxT5kVNkzpF/blEOv1XCwThc2JpmAYc LMEiyr7cC5ZEVkqWknhayt9LeL1Bpa/OsXfqbQqKbNT/IQkCMeINE7sq+uyOQGCOo8Oc=;
Received: from [64.71.6.2] (helo=[10.100.9.254]) by v2.bluepopcorn.net with esmtpsa (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from <fenton@bluepopcorn.net>) id 1qHofF-00030L-LW; Fri, 07 Jul 2023 09:50:38 -0700
From: Jim Fenton <fenton@bluepopcorn.net>
To: "Kyzer Davis (kydavis)" <kydavis@cisco.com>
Cc: Robert Sparks <rjsparks@nostrum.com>, dispatch@ietf.org, dispatch-chairs <dispatch-chairs@ietf.org>, "Gonzalo Salgueiro (gsalguei)" <gsalguei@cisco.com>, "Esteban Valverde (jovalver)" <jovalver@cisco.com>
Date: Fri, 07 Jul 2023 09:50:37 -0700
X-Mailer: MailMate (1.14r5852)
Message-ID: <F6498B81-E3FA-4B55-9B27-D08B6DE5645B@bluepopcorn.net>
In-Reply-To: <PH0PR11MB50290EF2C2EC7A2DAFC60A9FBB2DA@PH0PR11MB5029.namprd11.prod.outlook.com>
References: <7af70840a1b74a45827bbbea01eefd21@huawei.com> <PH0PR11MB50295418DAF17D94B1C9DBBCBB27A@PH0PR11MB5029.namprd11.prod.outlook.com> <dc0b078d-bfcd-53ab-c4c1-60242805755f@nostrum.com> <PH0PR11MB50290EF2C2EC7A2DAFC60A9FBB2DA@PH0PR11MB5029.namprd11.prod.outlook.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="=_MailMate_16C6A2FD-6EA4-455E-ABC8-09C0C923B5E6_="
Content-Transfer-Encoding: 8bit
Embedded-HTML: [{"plain":[379, 3295], "uuid":"5EA924EE-BAA7-4400-B016-AC5F8585E299"}]
Archived-At: <https://mailarchive.ietf.org/arch/msg/dispatch/_YVsHwz8MR9Dm5jcUYu4ReWvBAQ>
Subject: Re: [dispatch] IETF 117 - do you have something for DISPATCH?
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dispatch/>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Jul 2023 16:50:44 -0000

Kyzer,

Please run this by the mmusic chairs and see if they agree that this 
belongs in that WG. You’re on the dispatch agenda currently, but I 
would rather not take people’s time dispatching something that 
doesn’t need dispatching.

Please let us (dispatch-chairs) know what the result of your 
consultation is.

-Jim

On 7 Jul 2023, at 9:23, Kyzer Davis (kydavis) wrote:

> Hello Robert,
>
>> Why aren't you taking this straight to mmusic? Am I missing something 
>> that says that's not the obvious place for the work?
>
> Jim Fenton also mentioned this to me unicast.
>
> As a somewhat newer contributor to IETF I will state the “what goes 
> where” can be daunting since I am not familiar with all of the IETF 
> WG charters.
>
> I know from my previous experience I started with dispatch, presented 
> a brief overview of the topics, and the group of more tenured IETF 
> folks direct the work to the correct place.
>
> I figured the same would apply here.
>
>
>
> Checking mmusic WG charter it seems like a fit since RFC4568 was with 
> that group.
>
> I also see that avtcore WG has some SRTP items in their charter and 
> many authored SRTP documents. (I based most of my draft on the format 
> of RFC9335 authored by atvcore.)
>
>
>
> Thanks,
>
>
>
> From: Robert Sparks <rjsparks@nostrum.com>
> Sent: Friday, July 7, 2023 10:38 AM
> To: Kyzer Davis (kydavis) <kydavis@cisco.com>; Pengshuping (Peng 
> Shuping) <pengshuping=40huawei.com@dmarc.ietf.org>; dispatch@ietf.org
> Cc: dispatch-chairs <dispatch-chairs@ietf.org>; Gonzalo Salgueiro 
> (gsalguei) <gsalguei@cisco.com>; Esteban Valverde (jovalver) 
> <jovalver@cisco.com>
> Subject: Re: [dispatch] IETF 117 - do you have something for DISPATCH?
>
>
>
> Hi Kyzer (et. al.) -
>
> Why aren't you taking this straight to mmusic? Am I missing something 
> that says that's not the obvious place for the work?
>
> RjS
>
>
>
> On 6/27/23 7:31 AM, Kyzer Davis (kydavis) wrote:
>
> Hello,
>
>
>
> I would like to request a bit of dispatch time for the draft just 
> posted:
>
>  <https://datatracker.ietf.org/doc/draft-davis-valverde-srtp-assurance/> 
> https://datatracker.ietf.org/doc/draft-davis-valverde-srtp-assurance/
>
>
>
> I also plan to attend IETF 117 in person to represent.
>
>
>
> Thanks,
>
>
>
> From: dispatch  <mailto:dispatch-bounces@ietf.org> 
> <dispatch-bounces@ietf.org> On Behalf Of Pengshuping (Peng Shuping)
> Sent: Friday, June 16, 2023 1:09 AM
> To:  <mailto:dispatch@ietf.org> dispatch@ietf.org
> Cc: dispatch-chairs  <mailto:dispatch-chairs@ietf.org> 
> <dispatch-chairs@ietf.org>
> Subject: [dispatch] IETF 117 - do you have something for DISPATCH?
>
>
>
> Hi everyone,
>
>
>
> It's that time again - we're calling for agenda topics for our next 
> meeting at IETF 117 (22 - 28 Jul 2023). No matter how big or small, if 
> you have something you'd like dispatching or that you think will be of 
> interest to the ART AREA, get in touch and get involved.
>
>
>
> If you would like time at the meeting to discuss your work or ideas, 
> please email Jim and me. We're keen to hear from you!
>
>
>
> And if you're not really sure what this dispatching thing is for, or 
> if you have any questions about bringing new work, please get in touch 
> with us all the same - we're here to help.
>
>
>
> We look forward to hearing from you.
>
>
>
> PS. We have updated the DISPATCH WG wiki ( 
> <https://wiki.ietf.org/group/dispatch> 
> https://wiki.ietf.org/group/dispatch) to include more information on 
> how to prepare for attending the session and your presentations in 
> DISPATCH and so on. Hope they are helpful. If you have any suggestions 
> on improving this wiki page and adding more materials, please feel 
> free to email us. Thank you!
>
>
>
> Shuping & Jim