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

Richard Shockey <richard@shockey.us> Mon, 28 May 2018 18:43 UTC

Return-Path: <richard@shockey.us>
X-Original-To: stir@ietfa.amsl.com
Delivered-To: stir@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B057F127775 for <stir@ietfa.amsl.com>; Mon, 28 May 2018 11:43:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (768-bit key) header.d=shockey.us
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 gV3KM3xgB9Ca for <stir@ietfa.amsl.com>; Mon, 28 May 2018 11:43:12 -0700 (PDT)
Received: from outbound-ss-866.bluehost.com (outbound-ss-866.bluehost.com [69.89.22.43]) (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 13865126DFB for <stir@ietf.org>; Mon, 28 May 2018 11:43:12 -0700 (PDT)
Received: from cmgw10.unifiedlayer.com (unknown [10.9.0.10]) by gproxy1.mail.unifiedlayer.com (Postfix) with ESMTP id 8B54E176F2B for <stir@ietf.org>; Mon, 28 May 2018 12:24:57 -0600 (MDT)
Received: from box462.bluehost.com ([74.220.219.62]) by cmsmtp with ESMTP id NMpFf90H44N1cNMpFfsDJx; Mon, 28 May 2018 12:24:57 -0600
X-Authority-Reason: nr=8
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=shockey.us; s=default; h=Content-transfer-encoding:Content-type:Mime-version:In-Reply-To :References:Message-ID:To:From:Subject:Date:Sender:Reply-To:Cc: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=gpnSD4EdIbP8euq8pz00E2KLOd+2Faes+6R3XZEWw1Y=; b=oFUjalqc75X+IMwdRETbcBj7kG 0ilEIyIgpnlN2JEa6RKhQ17+zTJVY2qbovWW7XtvhpjkipeoZvBvrxwk2yTHF71dDmNhdQXb1tmq6 AV7URaxLt26WP9Wl7pw4u1FIO;
Received: from pool-173-79-80-207.washdc.fios.verizon.net ([173.79.80.207]:64775 helo=[192.168.1.155]) by box462.bluehost.com with esmtpa (Exim 4.89_1) (envelope-from <richard@shockey.us>) id 1fNMpE-001H5I-Vk for stir@ietf.org; Mon, 28 May 2018 12:24:57 -0600
User-Agent: Microsoft-MacOutlook/10.d.1.180523
Date: Mon, 28 May 2018 14:24:55 -0400
From: Richard Shockey <richard@shockey.us>
To: "stir@ietf.org" <stir@ietf.org>
Message-ID: <A261DB1C-1228-4972-A8F6-323BF9655046@shockey.us>
Thread-Topic: [dispatch] Need guidance on how to progress draft-york-dispatch-p-charge-info
References: <E6A16181E5FD2F46B962315BB05962D07D354B06@fcc.gov>
In-Reply-To: <E6A16181E5FD2F46B962315BB05962D07D354B06@fcc.gov>
Mime-version: 1.0
Content-type: text/plain; charset="UTF-8"
Content-transfer-encoding: quoted-printable
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - box462.bluehost.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - shockey.us
X-BWhitelist: no
X-Source-IP: 173.79.80.207
X-Source-L: No
X-Exim-ID: 1fNMpE-001H5I-Vk
X-Source:
X-Source-Args:
X-Source-Dir:
X-Source-Sender: pool-173-79-80-207.washdc.fios.verizon.net ([192.168.1.155]) [173.79.80.207]:64775
X-Source-Auth: richard+shockey.us
X-Email-Count: 2
X-Source-Cap: c2hvY2tleXU7c2hvY2tleXU7Ym94NDYyLmJsdWVob3N0LmNvbQ==
X-Local-Domain: yes
Archived-At: <https://mailarchive.ietf.org/arch/msg/stir/u26Vhp31amytbqNTC4eBfsarmsk>
Subject: [stir] FW: [dispatch] Need guidance on how to progress draft-york-dispatch-p-charge-info
X-BeenThere: stir@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Secure Telephone Identity Revisited <stir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/stir>, <mailto:stir-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/stir/>
List-Post: <mailto:stir@ietf.org>
List-Help: <mailto:stir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/stir>, <mailto:stir-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 28 May 2018 18:43:15 -0000

Here was the issue Henning was trying to deal with... in 2015 and those issues are still there. 

— 
Richard Shockey

Shockey Consulting LLC

Chairman of the Board SIP Forum

www.shockey.us

www.sipforum.org

richard<at>shockey.us

Skype-Linkedin-Facebook –Twitter  rshockey101

PSTN +1 703-593-2683

 

On 6/11/15, 1:02 PM, "Henning Schulzrinne" <Henning.Schulzrinne@fcc.gov>; wrote:

    Yes, carrying the charge number is important for various (arcane) settlement and rural call completion issues; see
    
    47 CFR 64.1601
    
    for one example:
    
    Intermediate providers within an interstate or intrastate call path that originates and/or terminates on the PSTN must pass unaltered to subsequent providers in the call path signaling information identifying the telephone number, or billing number, if different, of the calling party that is received with a call.
    
    https://www.law.cornell.edu/cfr/text/47/64.1601
    
    Henning
    ________________________________
    From: dispatch [dispatch-bounces@ietf.org] on behalf of Richard Shockey [richard@shockey.us]
    Sent: Thursday, June 11, 2015 11:49 AM
    To: Mary Barnes; Dan York
    Cc: dispatch@ietf.org
    Subject: Re: [dispatch] Need guidance on how to progress draft-york-dispatch-p-charge-info
    
    
    BTW It was my understanding that there is actually a regulatory requirement here.
    
    Henning, if I recall, mentioned this a while back. I can’t recall the context.
    
    From: Mary Barnes <mary.ietf.barnes@gmail.com<mailto:mary.ietf.barnes@gmail.com>>
    Date: Thursday, June 11, 2015 at 12:29 AM
    To: Dan York <york@isoc.org<mailto:york@isoc.org>>
    Cc: "dispatch@ietf.org<mailto:dispatch@ietf.org>" <dispatch@ietf.org<mailto:dispatch@ietf.org>>
    Subject: Re: [dispatch] Need guidance on how to progress draft-york-dispatch-p-charge-info
    
    The DISPATCH process is fairly clearly described on the wiki:
    https://tools.ietf.org/wg/dispatch/trac/wiki
    
    So, your option 1. as Robert points out isn't an option with the current process.  Option 2 could happen as part of the DISPATCH process and as others have noted seems the most likely outcome.  In the case of option 2, the usual process is to ask whether there are any concerns on the DISPATCH WG mailing list and get feedback from the WG participants.
    
    The challenge of course is that we've deprecated P-headers and this would be an exception and would have to be clearly documented as such, but I would worry about this opening the floodgate for additional P-headers.  We would need to be clear that this isn't the intent here.
    
    Regards,
    Mary.
    
    On Wed, Jun 10, 2015 at 2:06 PM, Dan York <york@isoc.org<mailto:york@isoc.org>> wrote:
    
    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:
    
    
    https://tools.ietf.org/html/draft-york-dispatch-p-charge-info-05
    
    
    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:
    
    
    http://www.iana.org/assignments/sip-parameters/sip-parameters.xhtml#sip-parameters-2
    
    
    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.)
    
    
    Thanks,
    
    Dan
    
    
    [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.
    
    
    
    _______________________________________________
    dispatch mailing list
    dispatch@ietf.org<mailto:dispatch@ietf.org>
    https://www.ietf.org/mailman/listinfo/dispatch
    
    
    _______________________________________________ dispatch mailing list dispatch@ietf.org<mailto:dispatch@ietf.org> https://www.ietf.org/mailman/listinfo/dispatch