Re: [V3] RIPT BoF approved for IETF 107 - Draft charter below

Jonathan Rosenberg <jdrosen@jdrosen.net> Tue, 18 February 2020 16:21 UTC

Return-Path: <jdrosen@jdrosen.net>
X-Original-To: v3@ietfa.amsl.com
Delivered-To: v3@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 118F112082D for <v3@ietfa.amsl.com>; Tue, 18 Feb 2020 08:21:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.696
X-Spam-Level:
X-Spam-Status: No, score=-1.696 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=neutral reason="invalid (public key: not available)" header.d=jdrosen.net
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nPXyj8sa8Ru8 for <v3@ietfa.amsl.com>; Tue, 18 Feb 2020 08:21:37 -0800 (PST)
Received: from se4i-iad1.servconfig.com (se4i-iad1.servconfig.com [173.231.241.39]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 21889120823 for <v3@ietf.org>; Tue, 18 Feb 2020 08:21:37 -0800 (PST)
Received: from ecbiz261.inmotionhosting.com ([173.231.209.30]) by se4-iad1.servconfig.com with esmtps (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.92) (envelope-from <jdrosen@jdrosen.net>) id 1j45cm-000Kbn-Q4 for v3@ietf.org; Tue, 18 Feb 2020 11:21:36 -0500
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=jdrosen.net ; s=default; h=Content-Type:Cc:To:Subject:Message-ID:Date:From:In-Reply-To: References:MIME-Version:Sender:Reply-To:Content-Transfer-Encoding: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=50mRPtcF4q3gziVI7dF/c63irEuh+2NNgKqKx9R8onk=; b=TgAFq9cZ+6424U01zeLomZXFEw xQ4aJaRKc7pWHo6Xk4H1Zo11/IOcUAZzfG97f0dLpFu5IgnfBjUw9CA1Rp6YGgUDj/lf4Bm+vtxq6 Syv1H1z1eNsip8oTw+75QqoG1baqH48iFkxFYCQjynFn35J5OCxInJUs+kKFDCmb5Djq4QX+hIlft IihyCmIf0UUI9MHUKUFbLsDImutFR0rFYLv5I9Vb1HfVFwZLFqt7D7k91s65NPADfCvA/v5p33sOw d0WE4dijCnEIRQBGkg4lE19DULM1b1AC719P2wfl9o0gbP9chj3F2byrd93Er+YIOKTJaiuwageSt lr9ecrCA==;
Received: from mail-io1-f48.google.com ([209.85.166.48]:44480) by ecbiz261.inmotionhosting.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.92) (envelope-from <jdrosen@jdrosen.net>) id 1j45cc-00AUrc-Ru for v3@ietf.org; Tue, 18 Feb 2020 11:21:28 -0500
Received: by mail-io1-f48.google.com with SMTP id z16so22891809iod.11 for <v3@ietf.org>; Tue, 18 Feb 2020 08:21:18 -0800 (PST)
X-Gm-Message-State: APjAAAUp9/l/6e3VcQ5hYTVCDKqxarMvsl8I1Vamfvj0ebT99GQhAnRC +Q8ZXVGAKhJ3OuqKf0OP0nItGya1RpivV8hmTlg=
X-Google-Smtp-Source: APXvYqwhqH05gateskv/Oa2xXrOZgdXTNZXVxhXPido3MCJSbIzNRvW2D0UUfj3unbk5p8KUro5Z1I3DaEDsr6wFnzY=
X-Received: by 2002:a6b:610e:: with SMTP id v14mr16338441iob.262.1582042878358; Tue, 18 Feb 2020 08:21:18 -0800 (PST)
MIME-Version: 1.0
References: <BYAPR06MB43914433BF91CE216E6123A6FB150@BYAPR06MB4391.namprd06.prod.outlook.com> <9d7c093f-45bb-f779-dcfc-1fce1b014611@usdonovans.com>
In-Reply-To: <9d7c093f-45bb-f779-dcfc-1fce1b014611@usdonovans.com>
From: Jonathan Rosenberg <jdrosen@jdrosen.net>
Date: Tue, 18 Feb 2020 11:21:09 -0500
X-Gmail-Original-Message-ID: <CA+23+fFN8Z=zDaNK88BnTFA-b5GkwYiF4Yhb8xvRcjH7C1yHCg@mail.gmail.com>
Message-ID: <CA+23+fFN8Z=zDaNK88BnTFA-b5GkwYiF4Yhb8xvRcjH7C1yHCg@mail.gmail.com>
To: Steve Donovan <srdonovan@usdonovans.com>
Cc: v3@ietf.org
Content-Type: multipart/alternative; boundary="000000000000c8cecf059edc0fd1"
X-OutGoing-Spam-Status: No, score=-1.0
X-Get-Message-Sender-Via: ecbiz261.inmotionhosting.com: authenticated_id: jdrosen+jdrosen.net/only user confirmed/virtual account not confirmed
X-Authenticated-Sender: ecbiz261.inmotionhosting.com: jdrosen@jdrosen.net
X-Originating-IP: 173.231.209.30
X-SpamExperts-Domain: ecbiz261.inmotionhosting.com
X-SpamExperts-Username: 173.231.209.30
Authentication-Results: servconfig.com; auth=pass smtp.auth=173.231.209.30@ecbiz261.inmotionhosting.com
X-SpamExperts-Outgoing-Class: ham
X-SpamExperts-Outgoing-Evidence: Combined (0.15)
X-Recommended-Action: accept
X-Filter-ID: Mvzo4OR0dZXEDF/gcnlw0UaqOYGQPGxXNcBH7FeyDZOpSDasLI4SayDByyq9LIhVUZbR67CQ7/vm /hHDJU4RXkTNWdUk1Ol2OGx3IfrIJKywOmJyM1qr8uRnWBrbSAGDVIBiLrYj5ZoIoy4PXHicFwFw 5HF8KiNxM6kSO29YenZLkYzevpyCu2IXrnvwT9/sOD1iTNszLoM5iEbcxRy+GrzXpowsUIBWsz7t tC2m2ThBbLcvEVRb/r9HWBYzE6OiUynZipmyZiM0lULr8PxcDYeuUgzgc3py4wwfFTjOngSpMgA1 FfmD5Q1Ri4JUCeduAwCaU+JKXuJDa3LaePMOFRkhzVJFWn887ct0NFXnFWKxnGmiI3p9NEdyvIai 1RA3FPo67MEDuAALBU22yFTfTjFLpPQ2bGaaic07uJ3vXyFtAA0UIYoHm1gwgFcgYa/4CwGqOUcw rXf55E8Tb8bmXq4yH8StrboPphDtmrtUkwms9uj8bOqE9zVJwqYsk3or8Gj2HmxmMxqxWK5EnsxU GLXTnONsqyI++u9UMf5U2lFyXMWcv2ZlvSNZcmGO3E8wIzvpj9IzyBpc10ZJwnPg5Vau74sFbhfo ZlF1GXLOQZeiMuAxhZQFg66KByWXQVR0dNESBXu9KorGA+vyegwJ6zKR6RgQ6scM/oDJnhhySxnS UjC8FhcgFHOAfCPQP05ugM5yDzctcfgaSyAJ9MhDnhMqABCuK7DVpOJr7QXPUVGQLHKUZefri0p8 f92Xww6vVgUVN12b1Ctfih74/Kdn2mre/hsBBxzR0ZxLcHZ9dOhQMekJkUzNnuOP/fdFk2Zt5DMn wo0WE0JrSVg2cSKswig7jhh/Fb63kdiJpuIhZTtQmX7chX285rlMjQH/0fIV9R/2gMGq0KWAzmMf +ibVDnPQOMCpsNjBCLwXzWC5g1Gci8JLiiOdckUewCJrmQRcNgZ00xRl+f8iOCsvtWSXG9hVBIXs M154ZZ32GUyS5252yqCXA5IXj4HepxxbQBGvUiB0+JkVifJS4++53jbBRHy4XRzMJndCfnj5VlMP x+smqJveimuPWrFNgyzondpF
X-Report-Abuse-To: spam@se1-lax1.servconfig.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/v3/h8kNq4Wdj_np7WOdesbZUGOjMHY>
Subject: Re: [V3] RIPT BoF approved for IETF 107 - Draft charter below
X-BeenThere: v3@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <v3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v3>, <mailto:v3-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v3/>
List-Post: <mailto:v3@ietf.org>
List-Help: <mailto:v3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v3>, <mailto:v3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Feb 2020 16:21:39 -0000

Great question Steve. The goal is to do it based on working group
consensus, as always.

This would be educated based on - the concrete proposal in the current
documents which defines exactly the scope that is being proposed right now.
This avoids making this a theoretical discussion because we have a starting
point.

This question is also why I'm working on this draft:
https://tools.ietf.org/html/draft-rosenberg-dispatch-ript-sipdiffs-00

which is yet incomplete but will present an analysis of the SIP extension
landscape to get a feel for what the proposed scope actually covers.



On Tue, Feb 18, 2020 at 10:34 AM Steve Donovan <srdonovan@usdonovans.com>
wrote:

> Jonathan, Cullen,
>
> For the following:
>
> "It is a non-goal of this working group to replicate all of SIP and its
> many extensions into HTTP. The group will limit itself to supporting the
> functionality in widespread actual usage today."
>
> How do you envision defining the "functionality that is in widespread
> actual usage today?"
>
> Do we need another working group deliverable to define what of existing
> SIP is in and what is out?
>
> Thanks,
>
> Steve
> --
> V3 mailing list
> V3@ietf.org
> https://www.ietf.org/mailman/listinfo/v3
>


-- 
Jonathan Rosenberg, Ph.D.
jdrosen@jdrosen.net
http://www.jdrosen.net