Re: [sipcore] RSeq and forking - Errata
Christer Holmberg <christer.holmberg@ericsson.com> Wed, 10 June 2015 21:15 UTC
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: sipcore@ietfa.amsl.com
Delivered-To: sipcore@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 125961ACE61 for <sipcore@ietfa.amsl.com>; Wed, 10 Jun 2015 14:15:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham
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 HNxe4isUtpRX for <sipcore@ietfa.amsl.com>; Wed, 10 Jun 2015 14:15:36 -0700 (PDT)
Received: from sesbmg23.ericsson.net (sesbmg23.ericsson.net [193.180.251.37]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AE7251A899E for <sipcore@ietf.org>; Wed, 10 Jun 2015 14:15:35 -0700 (PDT)
X-AuditID: c1b4fb25-f79b66d000001131-72-5578a8f5f75d
Received: from ESESSHC007.ericsson.se (Unknown_Domain [153.88.253.125]) by sesbmg23.ericsson.net (Symantec Mail Security) with SMTP id B2.82.04401.5F8A8755; Wed, 10 Jun 2015 23:15:33 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.72]) by ESESSHC007.ericsson.se ([153.88.183.39]) with mapi id 14.03.0210.002; Wed, 10 Jun 2015 23:15:33 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>, "sipcore@ietf.org" <sipcore@ietf.org>
Thread-Topic: [sipcore] RSeq and forking - Errata
Thread-Index: AdCjwjb6aIhPA9HcRsaaDgKN4yT4tA==
Date: Wed, 10 Jun 2015 21:15:32 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B1D8B8CA2@ESESSMB209.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [153.88.183.149]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrOLMWRmVeSWpSXmKPExsUyM+Jvre7XFRWhBjdazCxWbDjAavH1xyY2 ByaPv+8/MHksWfKTKYApissmJTUnsyy1SN8ugSvj0/GbrAVXNSvutp1jb2DcoNDFyMkhIWAi sa5lFyOELSZx4d56ti5GLg4hgaOMEpOPH2UGSQgJLGaUWLfKrIuRg4NNwEKi+582SFhEIFDi 6pIJYCXCAgYSP768YIGIG0qcPNHOAlIuIqAncbmnGiTMIqAqsfrvErASXgFfibXrvoGtZQRa +/3UGiYQm1lAXOLWk/lMEOcISCzZc54ZwhaVePn4HyuErSSx9vB2Foh6HYkFuz+xQdjaEssW vmaGmC8ocXLmE5YJjMKzkIydhaRlFpKWWUhaFjCyrGIULU4tTspNNzLWSy3KTC4uzs/Ty0st 2cQIDPmDW36r7mC8/MbxEKMAB6MSD6/CrPJQIdbEsuLK3EOM0hwsSuK8MzbnhQoJpCeWpGan phakFsUXleakFh9iZOLglGpgDL54NCgjs4Bxp9/T5cZT71s9Mvo353nWffuKmisZey/7MGmu yzztU87Xts12RstuqRlzVLvTBTydr/lqMLlHzMgUr15TEFzvPu+D7Hf/+LvhTDeSgt3nCO8v 8DvkHHE772rACcdDS/s0eYyOptuZ9M9SeFp+v7HzZN6LrZeT+v48NWQ+nuutxFKckWioxVxU nAgAzil+VVoCAAA=
Archived-At: <http://mailarchive.ietf.org/arch/msg/sipcore/DM8JN3oWR8yuZbRCluvv9syj62M>
Subject: Re: [sipcore] RSeq and forking - Errata
X-BeenThere: sipcore@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: SIP Core Working Group <sipcore.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sipcore>, <mailto:sipcore-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sipcore/>
List-Post: <mailto:sipcore@ietf.org>
List-Help: <mailto:sipcore-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sipcore>, <mailto:sipcore-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Jun 2015 21:15:38 -0000
Hi, Some time ago, this issue was raised, and it seems like we agreed on a way forward. My colleague created an errata, but as far as I know nothing has happened. http://www.rfc-editor.org/errata_search.php?rfc=3262&eid=4288 I guess we should agree and close the errata? Regards, Christer -----Original Message----- From: sipcore [mailto:sipcore-bounces@ietf.org] On Behalf Of Paul Kyzivat Sent: 11 February 2015 22:41 To: sipcore@ietf.org Subject: Re: [sipcore] RSeq and forking On 2/11/15 2:54 PM, Christer Holmberg wrote: > Hi Roland, > > We could add a clarifying note. > > But, I don't think the note should talk about "use-cases". It should > simply say that, if forking occurs, RSeq values are processed per > early dialog, independently from the RSeq values on other early dialogs. +1 Note that the same is true for CSeq. It would be a very stupid implementation that handled the CSeq per-dialog but not the RSeq. Thanks, Paul > Regards, > > Christer > > *From:*R.Jesske@telekom.de [mailto:R.Jesske@telekom.de] > *Sent:* 11 February 2015 11:20 > *To:* Christer Holmberg; aallen@blackberry.com; brett@broadsoft.com; > sipcore@ietf.org > *Subject:* AW: [sipcore] RSeq and forking > > Hi Christer, > > The change itself is OK for me. > > Since I like to have more explicit description I would like to have > more text (e.g. Note) pointing to the fact that other early dialogs > depending on the number of responses made reliable have other RSeq values. > > Proposal : > > "As a result, if the UAC receives another reliable provisional > > response to the same request ,<new>on a given > dialog</new>and its RSeq value is not one higher > > than the value of the sequence number, that response > MUST NOT be > > acknowledged with a PRACK, and MUST NOT be processed > further by the > > UAC. An implementation MAY discard the response, or > MAY cache the > > response in the hopes of receiving the missing > responses. <new>Note that for some use cases multiples early dialogs > (e.g. forking) with different RSeq exist.</new>" > > Best Regards > > Roland > > *Von:*sipcore [mailto:sipcore-bounces@ietf.org] *Im Auftrag von > *Christer Holmberg > *Gesendet:* Mittwoch, 11. Februar 2015 08:53 > *An:* Andrew Allen; Brett Tate; sipcore@ietf.org > <mailto:sipcore@ietf.org> > *Betreff:* Re: [sipcore] RSeq and forking > > Hi, > > So, are people ok with my suggested text? > > Regards, > > Christer > > *From:*Andrew Allen [mailto:aallen@blackberry.com] > *Sent:* 11. helmikuuta 2015 9:44 > *To:* Brett Tate; Christer Holmberg; sipcore@ietf.org > <mailto:sipcore@ietf.org> > *Subject:* RE: [sipcore] RSeq and forking > > +1 > > *From:*sipcore [mailto:sipcore-bounces@ietf.org] *On Behalf Of *Brett > Tate > *Sent:* Tuesday, February 10, 2015 6:38 AM > *To:* Christer Holmberg; sipcore@ietf.org <mailto:sipcore@ietf.org> > *Subject:* Re: [sipcore] RSeq and forking > > Hi, > > I agree that some vendors have misinterpreted the sentence (and other > aspects of the RFC such as if only 200 and 481 are valid responses to > a PRACK). > > The errata would mainly just be useful to quickly end debate with > those who think devices are somehow supposed to magically coordinate > RSeq generation with other devices when forking has occurred. > > *From:*sipcore [mailto:sipcore-bounces@ietf.org > <mailto:sipcore-bounces@ietf.org>] *On Behalf Of *Christer Holmberg > *Sent:* Tuesday, February 10, 2015 5:33 AM > *To:* sipcore@ietf.org <mailto:sipcore@ietf.org> > *Subject:* [sipcore] RSeq and forking > > Hi, > > There has been some confusion regarding RFC 3262 and forking, and I'd > like to ask whether people think an errata would be useful. > > The text in section 4 says: > > "As a result, if the UAC receives another reliable provisional > > response to the same request, and its RSeq value is > not one higher > > than the value of the sequence number, that response > MUST NOT be > > acknowledged with a PRACK, and MUST NOT be processed > further by the > > UAC. An implementation MAY discard the response, or > MAY cache the > > response in the hopes of receiving the missing responses." > > Now, in case of forking, in my opinion the UAC may receive the same > (or even lower) RSeq value on different early dialogs. But, there seem > to be some confusion around it. > > So, I wonder whether an errata would be useful, modifying the text to > something like: > > "As a result, if the UAC receives another reliable provisional > > response to the same request,<new>on a given > dialog</new>, > > and its RSeq value is not one higher..." > > Regards, > > Christer > > > > _______________________________________________ > sipcore mailing list > sipcore@ietf.org > https://www.ietf.org/mailman/listinfo/sipcore > _______________________________________________ sipcore mailing list sipcore@ietf.org https://www.ietf.org/mailman/listinfo/sipcore
- Re: [sipcore] RSeq and forking - Errata Christer Holmberg
- Re: [sipcore] RSeq and forking - Errata Christer Holmberg
- Re: [sipcore] RSeq and forking - Errata Paul Kyzivat
- Re: [sipcore] RSeq and forking - Errata Christer Holmberg
- Re: [sipcore] RSeq and forking - Errata Ben Campbell
- Re: [sipcore] RSeq and forking - Errata Christer Holmberg
- Re: [sipcore] RSeq and forking - Errata Paul Kyzivat
- Re: [sipcore] RSeq and forking - Errata Ben Campbell
- Re: [sipcore] RSeq and forking - Errata Paul Kyzivat
- Re: [sipcore] RSeq and forking - Errata Ben Campbell
- Re: [sipcore] RSeq and forking - Errata A. Jean Mahoney
- Re: [sipcore] RSeq and forking - Errata Christer Holmberg
- Re: [sipcore] RSeq and forking - Errata Christer Holmberg
- Re: [sipcore] RSeq and forking - Errata Paul Kyzivat
- Re: [sipcore] RSeq and forking - Errata Christer Holmberg
- Re: [sipcore] RSeq and forking - Errata Paul Kyzivat
- Re: [sipcore] RSeq and forking - Errata Christer Holmberg
- Re: [sipcore] RSeq and forking - Errata Christer Holmberg
- Re: [sipcore] RSeq and forking - Errata A. Jean Mahoney
- Re: [sipcore] RSeq and forking - Errata Dale R. Worley
- Re: [sipcore] RSeq and forking - Errata Paul Kyzivat
- Re: [sipcore] RSeq and forking - Errata Christer Holmberg
- Re: [sipcore] RSeq and forking - Errata Paul Kyzivat
- Re: [sipcore] RSeq and forking - Errata Gonzalo Salgueiro (gsalguei)
- Re: [sipcore] RSeq and forking - Errata Christer Holmberg
- Re: [sipcore] RSeq and forking - Errata Paul Kyzivat
- Re: [sipcore] RSeq and forking - Errata Dale R. Worley
- Re: [sipcore] RSeq and forking - Errata Christer Holmberg