[dispatch] Need guidance on how to progress draft-york-dispatch-p-charge-info

Dan York <york@isoc.org> Wed, 10 June 2015 19:06 UTC

Return-Path: <york@isoc.org>
X-Original-To: dispatch@ietfa.amsl.com
Delivered-To: dispatch@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com []) by ietfa.amsl.com (Postfix) with ESMTP id 1C5C21A8700 for <dispatch@ietfa.amsl.com>; Wed, 10 Jun 2015 12:06:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.002
X-Spam-Status: No, score=-0.002 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id 2kWOHtHSOIRW for <dispatch@ietfa.amsl.com>; Wed, 10 Jun 2015 12:06:38 -0700 (PDT)
Received: from na01-by2-obe.outbound.protection.outlook.com (mail-by2on0082.outbound.protection.outlook.com []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 657D41A86F3 for <dispatch@ietf.org>; Wed, 10 Jun 2015 12:06:38 -0700 (PDT)
Received: from CY1PR0601MB1657.namprd06.prod.outlook.com ( by CY1PR0601MB1659.namprd06.prod.outlook.com ( with Microsoft SMTP Server (TLS) id; Wed, 10 Jun 2015 19:06:36 +0000
Received: from CY1PR0601MB1657.namprd06.prod.outlook.com ([]) by CY1PR0601MB1657.namprd06.prod.outlook.com ([]) with mapi id 15.01.0184.014; Wed, 10 Jun 2015 19:06:36 +0000
From: Dan York <york@isoc.org>
To: "dispatch@ietf.org" <dispatch@ietf.org>
Thread-Topic: Need guidance on how to progress draft-york-dispatch-p-charge-info
Thread-Index: AQHQo6zx5yx2Tgh9VkKar7py3gFYdA==
Date: Wed, 10 Jun 2015 19:06:35 +0000
Message-ID: <CY1PR0601MB1657710F6E8509476D8C8373B7BD0@CY1PR0601MB1657.namprd06.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
authentication-results: ietf.org; dkim=none (message not signed) header.d=none;
x-ms-exchange-messagesentrepresentingtype: 1
x-originating-ip: []
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:CY1PR0601MB1659;
x-microsoft-antispam-prvs: <CY1PR0601MB165963FC0EEE705B21F9BDDAB7BD0@CY1PR0601MB1659.namprd06.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(601004)(5005006)(520003)(3002001); SRVR:CY1PR0601MB1659; BCL:0; PCL:0; RULEID:; SRVR:CY1PR0601MB1659;
x-forefront-prvs: 06036BD506
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(6009001)(52314003)(164054003)(5001960100002)(107886002)(66066001)(86362001)(110136002)(46102003)(40100003)(2501003)(33656002)(92566002)(5003600100002)(19625215002)(2900100001)(19580395003)(19627405001)(99286002)(2656002)(2351001)(74316001)(106116001)(50986999)(122556002)(230783001)(102836002)(15975445007)(76576001)(189998001)(16236675004)(5002640100001)(77156002)(450100001)(62966003)(87936001)(54356999); DIR:OUT; SFP:1101; SCL:1; SRVR:CY1PR0601MB1659; H:CY1PR0601MB1657.namprd06.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en;
Content-Type: multipart/alternative; boundary="_000_CY1PR0601MB1657710F6E8509476D8C8373B7BD0CY1PR0601MB1657_"
MIME-Version: 1.0
X-OriginatorOrg: isoc.org
X-MS-Exchange-CrossTenant-originalarrivaltime: 10 Jun 2015 19:06:35.8333 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 89f84dfb-7285-4810-bc4d-8b9b5794554f
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CY1PR0601MB1659
Archived-At: <http://mailarchive.ietf.org/arch/msg/dispatch/KIH3fkLsHEHaOodL3XDsbMjJhT4>
Subject: [dispatch] Need guidance on how to progress draft-york-dispatch-p-charge-info
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Wed, 10 Jun 2015 19:06:41 -0000

DISPATCH participants,

I could use some help/guidance about how to move my now-seemingly-ancient P-Charge-Info draft forward. The draft is at:


Way back in 2008, I first submitted the draft to the SIPPING WG. My goal was simply to *document the existing usage* of the P-Charge-Info SIP header per the then-relevant RFC 3427 so that the header could be listed in the IANA registry of SIP parameters at:


My employer at the time, Voxeo, was (and still is) a strong user of the header and encouraged me to document it so that others could use the header within private networks.  As an IETF participant and SIP advocate, I personally wanted to document P-Charge-Info so that perhaps people could find it and use that header instead of creating yet another private header.  Tolga Asveren of Sonus Networks joined on very early in the process because Sonus was (and presumably still is) also actively using the header.  Lots of other people  chimed in along the way.

After an initial flurry of commentary and changes on the SIPPING list from 2008-2010, there's a longer story of why it took so long... there was the RFC 3427bis process which became RFC 5727... life and job changes... much more...

Anyway, at this point in 2015 I just want to move the document along and get it published so that the header can be registered and, quite honestly, so that I can stop renewing the document every 6 months.  Given that I still get inquiries about this header from time to time and that it is still being used, I feel a certain responsibility to just "get this done" rather than simply abandoning the draft.

>From what I know, there are three ways I can move this forward to publication:

1. DISPATCH approval - this WG can approve the draft and send to the IESG; [1]

2. AD-SPONSORED - I can ask a friendly AD to help send this to the IESG;

3. INDIVIDUAL SUBMISSION - I can send this in to the independent stream editor.

Am I correct?  And if so, what would any of you suggest as the simplest path to checking this off as done?

Comments on the actual draft are of course also welcome, with the reminder that the aim of the draft was and is to document existing usage rather than to create a new header, etc.  (Because if it was to create a new header, the "P-" would be removed, etc.)



[1] And yes, I do realize there is actually a 4th path which is that DISPATCH could "dispatch" this draft off to some other WG and I could then bring it through *that* WG. And if that's the best path I'm glad to do that, too... I just want to get this finished.