Re: [dispatch] Progressing draft-holmberg-dispatch-rfc7315-updates as AD sponsored
Christer Holmberg <christer.holmberg@ericsson.com> Wed, 27 April 2016 15:07 UTC
Return-Path: <christer.holmberg@ericsson.com>
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 35D5E12D16B for <dispatch@ietfa.amsl.com>; Wed, 27 Apr 2016 08:07:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level:
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 M8ePbGpoAMst for <dispatch@ietfa.amsl.com>; Wed, 27 Apr 2016 08:07:30 -0700 (PDT)
Received: from sesbmg22.ericsson.net (sesbmg22.ericsson.net [193.180.251.48]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1A6F212D85B for <dispatch@ietf.org>; Wed, 27 Apr 2016 08:07:29 -0700 (PDT)
X-AuditID: c1b4fb30-f79486d0000069d0-9e-5720d5af3a46
Received: from ESESSHC013.ericsson.se (Unknown_Domain [153.88.183.57]) by sesbmg22.ericsson.net (Symantec Mail Security) with SMTP id 01.99.27088.FA5D0275; Wed, 27 Apr 2016 17:07:28 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.117]) by ESESSHC013.ericsson.se ([153.88.183.57]) with mapi id 14.03.0248.002; Wed, 27 Apr 2016 17:07:27 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Adam Roach <adam@nostrum.com>, "A. Jean Mahoney" <mahoney@nostrum.com>, "dispatch@ietf.org" <dispatch@ietf.org>
Thread-Topic: [dispatch] Progressing draft-holmberg-dispatch-rfc7315-updates as AD sponsored
Thread-Index: AQHReK0rXLsqd7cN3kOoNRzSlGqrZ5+TKEuAgAAob1CAAcb14IAF08iAgAM+FoD//9KdAIAAUJsA
Date: Wed, 27 Apr 2016 15:07:26 +0000
Message-ID: <D346AE07.79EE%christer.holmberg@ericsson.com>
References: <CAHBDyN7iOPZN_jjd0_E5r+UG1jswY=-y17pr0skvPq5bJ2SrpA@mail.gmail.com> <56DDDFCD.5040604@nostrum.com> <5717A753.3050903@nostrum.com> <7594FB04B1934943A5C02806D1A2204B37F6D05B@ESESSMB209.ericsson.se> <7594FB04B1934943A5C02806D1A2204B37F720BF@ESESSMB209.ericsson.se> <D343DAB9.7771%christer.holmberg@ericsson.com> <D34692DF.79BC%christer.holmberg@ericsson.com> <5720BC8A.5060709@nostrum.com>
In-Reply-To: <5720BC8A.5060709@nostrum.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.6.3.160329
x-originating-ip: [153.88.183.17]
Content-Type: text/plain; charset="euc-kr"
Content-ID: <5E1531BC18ED484EA155CBBA63233225@ericsson.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrMIsWRmVeSWpSXmKPExsUyM2K7pe6GqwrhBgt+cFns+buI3WLppAWs Fg2dK1kdmD2WLPnJ5DFr5xOWAKYoLpuU1JzMstQifbsErozWbyUFZ6wr/jV8YWpg7LDqYuTk kBAwkTj+ciobhC0mceHeeiCbi0NI4AijRMOfs+wQzhJGia6WU4xdjBwcbAIWEt3/tEEaRARK Jd6eeswKYgsLxErs+LaCCSIeJ3Gx8T4bhB0l8b39AVgNi4CqxKOZh5hBbF4BK4kPzSuhls1k ljh1cCbYfE4BbYmvm7lBahiBDvp+ag3YTGYBcYlbT+YzQRwqILFkz3lmCFtU4uXjf2DzRQX0 JPa9OA82RkJAUWJ5vxxEq5bElx/72CBsa4l73ZugbEWJKd0P2SHOEZQ4OfMJywRG8VlIts1C 0j4LSfssJO2zkLQvYGRdxShanFqclJtuZKSXWpSZXFycn6eXl1qyiREYdQe3/DbYwfjyueMh RgEORiUeXgVZhXAh1sSy4srcQ4wSHMxKIryiwJgV4k1JrKxKLcqPLyrNSS0+xCjNwaIkzpsd +S9MSCA9sSQ1OzW1ILUIJsvEwSnVwMj0pteRKWbaui1KNataPx6488j4kg7vGWWN6kzPjz2z 77XO9F+7xUTO9V5/1Im3WwpMD53lCllonrg9V+X/rJR1jZvP6rslWSq5/3s2WeDFwVUnjjGG sJSVurutf9LB1f5Ww+mYzeGXHpcsDhaEvU/VY34XvilGZ/rlEuGkg9fe/ys96pHeZa7EUpyR aKjFXFScCACz/YWPtgIAAA==
Archived-At: <http://mailarchive.ietf.org/arch/msg/dispatch/gRBBZU89yxGUjr5_VnHJR5PwjX0>
Subject: Re: [dispatch] Progressing draft-holmberg-dispatch-rfc7315-updates as AD sponsored
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.17
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: Wed, 27 Apr 2016 15:07:37 -0000
Hi, >Sure -- my suggestion was one for clarification. If 3GPP does, in fact, >intend to allow the header field in mid-dialog messages, then my >comment doesn't apply. > >But if they *do* intend to allow the field mid-dialog, I'm curious about >why it's forbidden in the current list of methods: save for some obscure >corner cases, all of the methods called out by name are sent mid-dialog, >and none of the un-named methods are. OPTIONS, BYE, REFER (with RFC7615) and re-INVITE can be sent in-dialog. I can’t give an answer here and now why the list looks like it does, but this is how it’s specified in 3GPP :) >Either way, it's just a suggestion. The hard block here is in the ACK >handling that I pointed out. Based on your comments, the new text would now say: "The P-Associated-URI header field can appear in SIP REGISTER 2xx responses. The P-Called-Party-ID header field can appear in SIP INVITE, OPTIONS, PUBLISH, REFER, SUBSCRIBE, and MESSAGE methods. The P-Visited-Network-ID header field can appear in all SIP methods except ACK, BYE, CANCEL, NOTIFY, PRACK, INFO and UPDATE. The P-Access-Network-Info header field can appear in all SIP methods and non-100 responses, except in CANCEL methods, CANCEL responses and ACK methods triggered by non-2xx responses. The P-Charging-Vector header field can appear in all SIP methods and non-100 responses, except in CANCEL methods, CANCEL responses and ACK methods triggered by non-2xx responses. The P-Charging-Function-Addresses header field can appear in all SIP methods and non-100 responses, except in ACK and CANCEL methods and CANCEL responses.” Regards, Christer > >/a > >On 4/27/16 08:01, Christer Holmberg wrote: >> Hi, >> >> One more thing: >> >> I guess we could also change ³all responses² to ³all non-100 responses², >> as 100 responses are also hop-to-hop (similar to ACKs triggered by >>non-2xx >> responses). >> >> Regards, >> >> Christer >> >> >> On 25/04/16 14:30, "Christer Holmberg" <christer.holmberg@ericsson.com> >> wrote: >> >>> Hi Adam, >>> >>> Are you ok with my suggested way forward? >>> >>> Regards, >>> >>> Christer >>> >>> >>> >>> On 21/04/16 22:43, "Christer Holmberg" <christer.holmberg@ericsson.com> >>> wrote: >>> >>>> Hi Adam, >>>> >>>> .... >>>> >>>>>> One additional review note that does not affect my expert review >>>>>> (treat it as a last-call comment): >>>>>> >>>>>> >>>>>> Add statement that the P-Visited-Network-ID header field >>>>>>cannot >>>>>> appear in the SIP NOTIFY, PRACK, INFO and UPDATE methods. >>>>>> >>>>>> It seems to me that it would be significantly more future proof to >>>>>> phase this as "...cannot appear in mid-dialog requests," as that >>>>>> appears to be the intention. The revised text then becomes something >>>>>> like: "The P-Visited-Network-ID header >>>>>> field can appear in all SIP methods except ACK and CANCEL; however, >>>>>>it >>>>>> cannot be sent in >any mid-dialog requests." >>>>> Seems reasonable, but I'll verify with my 3GPP delegates. >>>> I had a closer look at this, and I don't think we can forbid usage in >>>>all >>>> mid-dialog requests. >>>> >>>> For example, the header field is allowed in OPTIONS, that can be sent >>>> in-dialog. >>>> >>>> Also, the header field is allowed in REFER, and RFC 7614 defines a >>>> mechanism that allows in-dialog REFERs. >>>> >>>> re-INVITE is also tricky. The header field is generally allowed in >>>>INVITE >>>> requests, but there is no text explicitly disallowing it in >>>>re-INVITEs. >>>> >>>> Whether it makes sense to include the header field in the methods >>>>above I >>>> don't know (3GPP does allow them), but as the purpose is only to align >>>> 7315 with 3455 I'd suggest we keep the text as it is. >>>> >>>> >>>> Regards, >>>> >>>> Christer >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> On 3/7/16 14:08, A. Jean Mahoney wrote: >>>> Since this draft updates RFC 7315, which required expert review of its >>>> header fields, Adam Roach will be conducting an expert review of this >>>> draft according to the guidance given in RFC 5727. >>>> >>>> Thanks, >>>> >>>> Jean >>>> >>>> >>>> On 3/7/16 9:33 AM, Mary Barnes wrote: >>>> >>>> Hi folks, >>>> >>>> This document has been proposed to be progressed as AD sponsored: >>>> >>>>https://datatracker.ietf.org/doc/draft-holmberg-dispatch-rfc7315-update >>>>s/ >>>> The document has been carefully reviewed and it is now ready to move >>>> forward - Jean Mahoney is the shepherd. >>>> >>>> I don't anticipate anyone would have concerns about this decision, >>>>given >>>> that's how RFC 7315 was progressed and this update has actually been >>>>much >>>> more carefully reviewed. However, f anyone has any final comments, >>>> please post no later than Friday, March 11th, 2016. Note, that you >>>>will >>>> also still have IETF LC to provide any comments. >>>> >>>> Regards, >>>> Mary. >>>> >>>> >>>> _______________________________________________ >>>> dispatch mailing list >>>> dispatch@ietf.org >>>> https://www.ietf.org/mailman/listinfo/dispatch >>>> >>>> _______________________________________________ >>>> dispatch mailing list >>>> dispatch@ietf.org >>>> https://www.ietf.org/mailman/listinfo/dispatch >>>> >>>> _______________________________________________ >>>> dispatch mailing list >>>> dispatch@ietf.org >>>> https://www.ietf.org/mailman/listinfo/dispatch >
- [dispatch] Progressing draft-holmberg-dispatch-rf… Mary Barnes
- Re: [dispatch] Progressing draft-holmberg-dispatc… A. Jean Mahoney
- Re: [dispatch] Progressing draft-holmberg-dispatc… marianne.mohali
- Re: [dispatch] Progressing draft-holmberg-dispatc… Georg Mayer
- Re: [dispatch] Progressing draft-holmberg-dispatc… DOLLY, MARTIN C
- Re: [dispatch] Progressing draft-holmberg-dispatc… DOLLY, MARTIN C
- Re: [dispatch] Progressing draft-holmberg-dispatc… A. Jean Mahoney
- Re: [dispatch] Progressing draft-holmberg-dispatc… Andrew Allen
- Re: [dispatch] Progressing draft-holmberg-dispatc… Drage, Keith (Nokia - GB)
- Re: [dispatch] Progressing draft-holmberg-dispatc… marianne.mohali
- Re: [dispatch] Progressing draft-holmberg-dispatc… Shida Schubert
- Re: [dispatch] Progressing draft-holmberg-dispatc… Adam Roach
- Re: [dispatch] Progressing draft-holmberg-dispatc… Christer Holmberg
- Re: [dispatch] Progressing draft-holmberg-dispatc… Christer Holmberg
- Re: [dispatch] Progressing draft-holmberg-dispatc… Christer Holmberg
- Re: [dispatch] Progressing draft-holmberg-dispatc… Christer Holmberg
- Re: [dispatch] Progressing draft-holmberg-dispatc… Adam Roach
- Re: [dispatch] Progressing draft-holmberg-dispatc… Christer Holmberg
- Re: [dispatch] Progressing draft-holmberg-dispatc… Paul Kyzivat
- Re: [dispatch] Progressing draft-holmberg-dispatc… Christer Holmberg
- Re: [dispatch] Progressing draft-holmberg-dispatc… Paul Kyzivat
- Re: [dispatch] Progressing draft-holmberg-dispatc… Christer Holmberg