
From nobody Thu Feb  3 15:53:08 2022
Return-Path: <session-request@ietf.org>
X-Original-To: sipcore@ietf.org
Delivered-To: sipcore@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 0F7E23A0DCB; Thu,  3 Feb 2022 15:53:06 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: IETF Meeting Session Request Tool <session-request@ietf.org>
To: <session-request@ietf.org>
Cc: mahoney@nostrum.com, sipcore-chairs@ietf.org, sipcore@ietf.org, superuser@gmail.com
X-Test-IDTracker: no
X-IETF-IDTracker: 7.44.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <164393238586.18146.16939308518217543360@ietfa.amsl.com>
Date: Thu, 03 Feb 2022 15:53:05 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/sipcore/IePBcZ-_GsT8imhQg3v7W_mFDFY>
Subject: [sipcore] sipcore - Not having a session at IETF 113
X-BeenThere: sipcore@ietf.org
X-Mailman-Version: 2.1.29
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: <https://mailarchive.ietf.org/arch/browse/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: Thu, 03 Feb 2022 23:53:06 -0000

Jean Mahoney, a chair of the sipcore working group, indicated that the sipcore working group does not plan to hold a session at IETF 113.

This message was generated and sent by the IETF Meeting Session Request Tool.




From nobody Wed Feb 16 06:12:38 2022
Return-Path: <eliot@robinsonmanagementservice.com>
X-Original-To: sipcore@ietfa.amsl.com
Delivered-To: sipcore@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CC1623A132A for <sipcore@ietfa.amsl.com>; Wed, 16 Feb 2022 06:12:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level: 
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=robinsonmanagementservice.com
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 CwAZUskL4rFl for <sipcore@ietfa.amsl.com>; Wed, 16 Feb 2022 06:12:30 -0800 (PST)
Received: from mail-oo1-xc30.google.com (mail-oo1-xc30.google.com [IPv6:2607:f8b0:4864:20::c30]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CF13B3A1331 for <sipcore@ietf.org>; Wed, 16 Feb 2022 06:12:30 -0800 (PST)
Received: by mail-oo1-xc30.google.com with SMTP id e19-20020a4ab993000000b0031a98fe3a9dso1982223oop.6 for <sipcore@ietf.org>; Wed, 16 Feb 2022 06:12:30 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=robinsonmanagementservice.com; s=google; h=mime-version:from:date:message-id:subject:to:cc; bh=7f2WDu1baQJWi+sSZAEpWuoxuz8miWHJfcZucHvDb+I=; b=Jd3V5s5bBvgsNjPzglYQC3nPbliebwaJM9q7kFFtH1krzt/QVKXCdSFkpTFaQMzWdK SsOY8S40aaLo8UkkyUsOq8ylsjgL/hNjia9HPEsfUmIEhNZ9Oirtp1SAlTJoHT27rCxl z+6rzuVRDVASe/RQNg+BaPHhKLIoJpNz0UYvHt7/OJUdqaelVEhoUCBXQOUZ+gc1Ti3n 96ogI++YLaUYaVS1W4Sp6EaajCOnXnSLG2XsCcRrocJ86A8sS1pdzuNS6XjoJWYv8TfY 92wOLbAR98wvwsYrInC5oadj7oJgP/6ifcuubae1QHCjJ6jUxPXehUTq0zsAlg9BMrli okgQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:from:date:message-id:subject:to:cc; bh=7f2WDu1baQJWi+sSZAEpWuoxuz8miWHJfcZucHvDb+I=; b=s28smgz27o97JCVQnAHoYCzyZjCsATujv7mlXLpIpJm0rqfVYafAY0/41UmrcBgNMr CfA4rhDeRXWQJZHGS74gsyjlntQOOLpS036vx/GFPhZndTCq1oiKU4B2TFY4AGaBh+5C gxzImLKq2PuwyorTyPif+/ylAtgbFB8x+e6E9slr19V6gBgSyxizR6N3E0vlswxYfbQT kQgWknmobAk5PSv+BucbWpvw67KOHX3S93XimbpFzQslVceKHIW3viWRuP3G3K0q0h7I /y/E1OzZOIv89s+skDfU9vN5G7++49nyiUW7QMXZNMg12yIgSzH77U7ZEmVoFOic8o+r WRaQ==
X-Gm-Message-State: AOAM530DSlw+CHrrvERDK/g9SIlJj8NmQMVLgSKqCsBDk5ognhPIPEIQ MLAbIn8RJq2nt2aGaV+v1hN38NrsmRXZcOBBUUWgL7LbrfGPWA==
X-Google-Smtp-Source: ABdhPJzGBb/OgJPuXChIZoeKX9ja8WxvXF5m2M/QiGXGkkF9WfeulyXKrpX/FrKduwAcMqhS8OsvPCX12W5FbvIc8dg=
X-Received: by 2002:a05:6870:63a7:b0:d1:331d:af99 with SMTP id t39-20020a05687063a700b000d1331daf99mr578201oap.72.1645020748572; Wed, 16 Feb 2022 06:12:28 -0800 (PST)
MIME-Version: 1.0
From: Eliot Robinson <eliot@robinsonmanagementservice.com>
Date: Wed, 16 Feb 2022 06:12:17 -0800
Message-ID: <CA+B6FrOa_Lr0VqZE+RFODb5LpLSqz7KDbsnCoBMPCYKgMMxu7Q@mail.gmail.com>
To: sipcore@ietf.org
Cc: eburger@standardstract.com, nagdab@gmail.com, jerusha.burnett@fcc.gov
Content-Type: multipart/alternative; boundary="0000000000005df8ea05d8233d5b"
Archived-At: <https://mailarchive.ietf.org/arch/msg/sipcore/kTwV4ljD2Zw0HQ2WcHgnDQ15je8>
Subject: [sipcore] request for comments 8688
X-BeenThere: sipcore@ietf.org
X-Mailman-Version: 2.1.29
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: <https://mailarchive.ietf.org/arch/browse/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, 16 Feb 2022 14:12:36 -0000

--0000000000005df8ea05d8233d5b
Content-Type: text/plain; charset="UTF-8"

hi,

there are industry groups representing callers and carriers actively
commenting on the appropriate sip response code to use in the case a call
is rejected based on an analytics engine.  these comments are in the fcc
consumer and governmental affairs bureau's sixth further notice of
proposed rulemaking in advanced methods to target and eliminate unlawful
robocalls docket no.17-59.
ECFS Filings Results (fcc.gov)
<https://www.fcc.gov/ecfs/search/filings?q=(%22robocalls%22)&sort=date_disseminated,DESC>


fcc originally proposed the use of sip response code 608 for calls blocked
based on an analytics engine but some carriers objected because of
alleged complexity.  some carriers asserted that sip response code 603 was
good enough.

fcc has relented to permit sip code 603 to be used for an undefined period
in addition to 608.

i responded that sip response code 603 is only for user call rejection.
<https://ecfsapi.fcc.gov/file/10214644920309/rms%20USTelecom%20-%20Comments%20on%20Blocking%20Notification%20Sixth%20FNPRM%20-%20Final.pdf>
rfc 3261 states "The callees's machine was successfully contacted but the
user explicitly does not wish to or cannot participate..." it is confusing
to use sip code 603 (user rejection) and stating in a header field it is
not user rejection but analytics engine rejection.  this is like saying i
want vanilla ice cream but what i really want is chocolate ice cream.

will ietf consider these fcc proposals and industry comments and respond
with appropriate informational or standards track rfc?

many thanks to the ietf for making sip a reality.

eliot

-- 
Eliot Steele Robinson
Robinson Management Service
4290 Bella Cascada Street
Las Vegas, NV 89135-2436
702-960-2463 (cell) 702-330-9921 (fax)
Eliot@RobinsonManagementService.com
https://www.RobinsonManagementService.com
DUNS 079879598 CAGE 7EEU6 JCP 0073645

--0000000000005df8ea05d8233d5b
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">hi,=C2=A0<div><br></div><div>there are industry groups rep=
resenting callers and carriers actively commenting on the appropriate=C2=A0=
sip response code to use in the case a call is rejected based on an analyti=
cs engine.=C2=A0 these=C2=A0comments are in the fcc consumer and government=
al affairs bureau&#39;s=C2=A0sixth=C2=A0further notice of proposed=C2=A0rul=
emaking in advanced methods to target and eliminate unlawful robocalls dock=
et=C2=A0no.17-59.=C2=A0<br><div><a href=3D"https://www.fcc.gov/ecfs/search/=
filings?q=3D(%22robocalls%22)&amp;sort=3Ddate_disseminated,DESC">ECFS Filin=
gs Results (fcc.gov)</a>=C2=A0<div><br></div><div><div>fcc originally propo=
sed=C2=A0the use of sip response code 608 for calls blocked based on an ana=
lytics engine but some carriers objected because of alleged=C2=A0complexity=
.=C2=A0 some carriers asserted that sip response code 603 was good enough.=
=C2=A0=C2=A0<br></div><div><br></div><div>fcc has relented to permit sip co=
de 603 to be used for an undefined period in addition to 608.</div><div><br=
></div><div><a href=3D"https://ecfsapi.fcc.gov/file/10214644920309/rms%20US=
Telecom%20-%20Comments%20on%20Blocking%20Notification%20Sixth%20FNPRM%20-%2=
0Final.pdf">i responded that sip response code 603 is only for user call re=
jection.</a>=C2=A0 rfc 3261 states &quot;The callees&#39;s machine was succ=
essfully contacted but the user explicitly does not wish to or cannot parti=
cipate...&quot; it is confusing to use sip code 603 (user rejection) and st=
ating in a header field it is not user rejection but analytics engine rejec=
tion.=C2=A0 this is like saying i want vanilla ice cream but what i really =
want is chocolate ice cream.</div><div><br></div><div>will ietf consider th=
ese fcc proposals and industry comments and respond with appropriate inform=
ational or standards track rfc?<br></div><div><br></div><div>many thanks to=
 the ietf for making sip a reality.</div><div><br></div><div>eliot=C2=A0=C2=
=A0<br clear=3D"all"><div><br></div>-- <br><div dir=3D"ltr" class=3D"gmail_=
signature" data-smartmail=3D"gmail_signature"><div dir=3D"ltr">Eliot Steele=
 Robinson<div>Robinson Management Service</div><div>4290 Bella Cascada Stre=
et</div><div>Las Vegas, NV 89135-2436</div><div>702-960-2463 (cell) 702-330=
-9921 (fax)</div><div>Eliot@RobinsonManagementService.com</div><div><a href=
=3D"https://www.RobinsonManagementService.com" target=3D"_blank">https://ww=
w.RobinsonManagementService.com</a></div><div>DUNS 079879598 CAGE 7EEU6 JCP=
 0073645</div></div></div></div></div></div></div></div>

--0000000000005df8ea05d8233d5b--


From nobody Sun Feb 27 00:04:00 2022
Return-Path: <esfandiari.m84@gmail.com>
X-Original-To: sipcore@ietfa.amsl.com
Delivered-To: sipcore@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DDE3A3A0A0A for <sipcore@ietfa.amsl.com>; Sun, 27 Feb 2022 00:03:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.359
X-Spam-Level: 
X-Spam-Status: No, score=-5.359 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, FROM_FMBLA_NEWDOM=1.498, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 68wk-lddMHLf for <sipcore@ietfa.amsl.com>; Sun, 27 Feb 2022 00:03:55 -0800 (PST)
Received: from mail-pj1-x102a.google.com (mail-pj1-x102a.google.com [IPv6:2607:f8b0:4864:20::102a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2902F3A0C55 for <sipcore@ietf.org>; Sun, 27 Feb 2022 00:03:55 -0800 (PST)
Received: by mail-pj1-x102a.google.com with SMTP id p3-20020a17090a680300b001bbfb9d760eso12115237pjj.2 for <sipcore@ietf.org>; Sun, 27 Feb 2022 00:03:55 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=3cFoqWD0c2aFu11czqFENThq1eqvXbbQNnA7Gz2qcv0=; b=m7RB4jgjhA0vM4NqhirVM16f11ADd4pi8+oe/3IKFDdmc1xKGTUy/wsxesT9LnQoSl 4sveJ/zJke+YRsEZ+kNOxEkBvQl3NmX73BSxr+9RfZ9y2QkTaqhoBprudNAwkyMARbtM WvihUlUwK8jrv05cPB43i3LIMJG2Nb1MeM8KQbYxwpXbPRmTedqGdp8dRvB0+/dEdQGD OP81gdNjM3rT5FYko/o7UyhGKN6jTq9JXxjkCtw55MEJPtgXaglfagONIUQ2lmWIEdIe kxIXWIx7QyeUDVC7W4hUm6KT59AT7YGVYwfuUmkov0oGad7sCcOu2lnJm3XU2KYCDIWD 72nw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=3cFoqWD0c2aFu11czqFENThq1eqvXbbQNnA7Gz2qcv0=; b=ycYBAFKnG1cOvoJEMZYc+Da+3RNRii7bKTrITYEX0ASPB1/bwuDiG6cpWcvkJlgfyv 73CKR3RTURWHz/ZAIk9GTnQUFpxUUomI2S58ll9eqwy4IbDGTDAgOPK0jSCKIwwSys7j d7aE8x6HwaFzUznmEhMTiAerpFIfZ9n6Z2cAVcBT7AQVGvDH7N337edVadMS10I5yabl u5ehNLvx+yDxNZRtpaBbZ6eI4XMxgwthmc0f3zIERwXQnti+ClU/03hgyfKmwYWJIIMp HpAbtmB1YoLHcZ7ct22ojsV+TsTm8Ehmccs2uiEM8cNfiaNQOmug7ZFyYFkS/eZ2cSZn RTZw==
X-Gm-Message-State: AOAM530+gNe1hKXh4cBom16DwUZXCg3haN15E5rAgWC4aMRGOR2MON0N JGgsjYd15XHVS0RXHXKzvuuWmjIJrBgr1Y6w+y47RNAtSRQ=
X-Google-Smtp-Source: ABdhPJyK43ayD6phjkhJsu/YjNJhXWeb4CvEE6lP7xFehnyZ6p4szAjR6NXm0JU+339vkOXfSDoBFXDpE7qmubDGoQs=
X-Received: by 2002:a17:90a:7bca:b0:1bc:8fe6:fbeb with SMTP id d10-20020a17090a7bca00b001bc8fe6fbebmr11116859pjl.28.1645949034023; Sun, 27 Feb 2022 00:03:54 -0800 (PST)
MIME-Version: 1.0
References: <CA+8sMAwvpid_N2iFL4c9YRNkLkFNiceaYL2s_-JSXOO31es0=Q@mail.gmail.com> <f0791224-bab5-b2b0-5534-181f6fc85305@opensips.org> <CA+8sMAwn5kQThg5nsfD9_jdpWXscxgesqSmuNmx4jS6cUfqZfQ@mail.gmail.com> <d6a0893e-cede-af20-87dc-35e616796f29@opensips.org> <CA+8sMAysA9iW7GLvVvadBo7V6nP7dNZDXp6opwojZi_MU84Zyg@mail.gmail.com> <HE1PR07MB44410C2ED63DD91F691842C4937C9@HE1PR07MB4441.eurprd07.prod.outlook.com> <CA+8sMAxLESZ-GDC5XdZMj+dwfZNjgyj83QYQ5=AcqpbRwXLA3Q@mail.gmail.com> <CA+8sMAz0KCqMZzz5QFpnuVYEj_YKXvr2ugDrghfPCjGW4YX=NQ@mail.gmail.com> <CA+8sMAxiWwVdZ1F2cd8x07gHVzfdPPRcZbo3do6mLuz7qNo_sA@mail.gmail.com> <CA7ACB45-7392-434B-890F-AD0752A00B2B@brianrosen.net> <CA+8sMAwASesT2msprRfHzY6t9+h2q8h2ZgBXZmHjt4Hcfi5z7A@mail.gmail.com>
In-Reply-To: <CA+8sMAwASesT2msprRfHzY6t9+h2q8h2ZgBXZmHjt4Hcfi5z7A@mail.gmail.com>
From: "Mojtaba Esfandiari.S" <esfandiari.m84@gmail.com>
Date: Sun, 27 Feb 2022 11:33:41 +0330
Message-ID: <CA+8sMAx5-q3onjpdQBQ1XESP=ST8hRHLgDiGeja=cS4gDZnCfQ@mail.gmail.com>
To: Brian Rosen <br@brianrosen.net>
Cc: sipcore@ietf.org
Content-Type: multipart/alternative; boundary="0000000000007dd45e05d8fb5f3b"
Archived-At: <https://mailarchive.ietf.org/arch/msg/sipcore/I1_VDjoq4QWFpaDl709esaXDIVg>
Subject: Re: [sipcore] Exception in RFC 3261 document
X-BeenThere: sipcore@ietf.org
X-Mailman-Version: 2.1.29
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: <https://mailarchive.ietf.org/arch/browse/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: Sun, 27 Feb 2022 08:04:00 -0000

--0000000000007dd45e05d8fb5f3b
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hello there,
What up about the decision of this Exception in RFC3261 in section (8.1.1.5
CSeq)?
Thanks

On Thu, Dec 23, 2021 at 6:17 PM Mojtaba Esfandiari.S <
esfandiari.m84@gmail.com> wrote:

> Many thanks.
>
> On Thu, Dec 23, 2021, 18:05 Brian Rosen <br@brianrosen.net> wrote:
>
>> No, we will deal with the errata and decide what to do.
>>
>> Brian (co-chair of SIPCORE)
>>
>> On Dec 23, 2021, at 5:03 AM, Mojtaba Esfandiari.S <
>> esfandiari.m84@gmail.com> wrote:
>>
>> Hello All,
>> I have reported this problem here (sipcore mailing list) and the new
>> Errata for confirmation.
>> Should I try more to report this?
>> cheers
>>
>> On Wed, Dec 22, 2021 at 1:46 AM Mojtaba Esfandiari.S <
>> esfandiari.m84@gmail.com> wrote:
>>
>>> https://www.rfc-editor.org/errata_search.php?rfc=3D3261&eid=3D6793
>>>
>>> On Wed, Dec 22, 2021 at 1:22 AM Mojtaba Esfandiari.S <
>>> esfandiari.m84@gmail.com> wrote:
>>>
>>>> Sure,
>>>> I have sent my issue to the SIPCore list and also have reported new
>>>> Errata.
>>>> Thanks
>>>> Best Regards.
>>>> Mojtaba
>>>>
>>>> On Tue, Dec 21, 2021 at 11:38 PM Christer Holmberg <
>>>> christer.holmberg@ericsson.com> wrote:
>>>>
>>>>> Hi Mojtaba,
>>>>>
>>>>>
>>>>>
>>>>> After an initial thought, your suggested clarification to section
>>>>> 8.1.1.5 seems correct. It could perhaps be more generic, though, and
>>>>> e.g.,say that specific procedures may define rules regarding the CSeq
>>>>> value. The 401/407 case could then be mentioned as an example.
>>>>>
>>>>>
>>>>>
>>>>> In any case, may I suggest that you send your issue to the SIPCORE
>>>>> list?
>>>>>
>>>>>
>>>>>
>>>>> Regards,
>>>>>
>>>>>
>>>>>
>>>>> Christer
>>>>>
>>>>>
>>>>>
>>>>> *From:* sipcore <sipcore-bounces@ietf.org> *On Behalf Of *Mojtaba
>>>>> Esfandiari.S
>>>>> *Sent:* tiistai 21. joulukuuta 2021 12.19
>>>>> *To:* Liviu Chircu <liviu@opensips.org>
>>>>> *Cc:* dispatch@ietf.org; sipcore@ietf.org
>>>>> *Subject:* Re: [sipcore] Exception in RFC 3261 document
>>>>>
>>>>>
>>>>>
>>>>> Actually, the UE is obeying the RFC 3261, But the SEMS project is not
>>>>> RFC 3261 compliant.
>>>>>
>>>>> It occurs because for 401 (Unauthorized) or 407 (Proxy Authentication
>>>>> Required) response, the value of CSeq does not change.
>>>>>
>>>>> So for more clarity and more understanding, It would be nice to have =
a
>>>>> quiet bit of update in RFC 3261 section 8.1.1.5.
>>>>>
>>>>> For example, the word "arbitrary" in the CSeq value may be confused
>>>>> with the same value as before.
>>>>>
>>>>> Thanks
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> On Tue, Dec 21, 2021 at 8:25 AM Liviu Chircu <liviu@opensips.org>
>>>>> wrote:
>>>>>
>>>>> On 20.12.2021 23:59, Mojtaba Esfandiari.S wrote:
>>>>> > The UE sends its request to Sems, then Sems relay the request to
>>>>> > Asterisk server. because in all INVITE messages, the Sems used the
>>>>> > same CSeq value (CSeq: 10 INVITE), asterisk goes to LOOP for
>>>>> > authentication UE.
>>>>>
>>>>> Then the UE is not RFC 3261-compliant, as it is disobeying the
>>>>> additional restrictions of =C2=A7 22.2.
>>>>>
>>>>> --
>>>>> Liviu Chircu
>>>>> www.twitter.com/liviuchircu
>>>>> <https://protect2.fireeye.com/v1/url?k=3D31323334-501d5122-313273af-4=
54445555731-742427605f27b27a&q=3D1&e=3D15584eeb-52e0-4596-a64d-ab25cbbb7dcb=
&u=3Dhttp%3A%2F%2Fwww.twitter.com%2Fliviuchircu>
>>>>> | www.opensips-solutions.com
>>>>> <https://protect2.fireeye.com/v1/url?k=3D31323334-501d5122-313273af-4=
54445555731-db93e02ae851094d&q=3D1&e=3D15584eeb-52e0-4596-a64d-ab25cbbb7dcb=
&u=3Dhttp%3A%2F%2Fwww.opensips-solutions.com%2F>
>>>>>
>>>>> _______________________________________________
>> sipcore mailing list
>> sipcore@ietf.org
>> https://www.ietf.org/mailman/listinfo/sipcore
>>
>>
>>

--0000000000007dd45e05d8fb5f3b
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>Hello there,</div><div>What up about the decision of =
this Exception in RFC3261 i<span>n section (8.1.1.5 CSeq)?<br></span></div>=
<div><span>Thanks<br></span></div></div><br><div class=3D"gmail_quote"><div=
 dir=3D"ltr" class=3D"gmail_attr">On Thu, Dec 23, 2021 at 6:17 PM Mojtaba E=
sfandiari.S &lt;<a href=3D"mailto:esfandiari.m84@gmail.com">esfandiari.m84@=
gmail.com</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=
=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding=
-left:1ex"><div dir=3D"auto">Many thanks.=C2=A0</div><br><div class=3D"gmai=
l_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Thu, Dec 23, 2021, 18:05 =
Brian Rosen &lt;<a href=3D"mailto:br@brianrosen.net" target=3D"_blank">br@b=
rianrosen.net</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" sty=
le=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);paddi=
ng-left:1ex"><div style=3D"overflow-wrap: break-word;">No, we will deal wit=
h the errata and decide what to do.<div><br></div><div>Brian (co-chair of S=
IPCORE)<br><div><br><blockquote type=3D"cite"><div>On Dec 23, 2021, at 5:03=
 AM, Mojtaba Esfandiari.S &lt;<a href=3D"mailto:esfandiari.m84@gmail.com" r=
el=3D"noreferrer" target=3D"_blank">esfandiari.m84@gmail.com</a>&gt; wrote:=
</div><br><div><div dir=3D"ltr"><div>Hello All,</div><div> I have reported =
this problem here (sipcore mailing list) and the new Errata for confirmatio=
n.</div><div>Should I try more to report this?</div><div>cheers<br></div></=
div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On=
 Wed, Dec 22, 2021 at 1:46 AM Mojtaba Esfandiari.S &lt;<a href=3D"mailto:es=
fandiari.m84@gmail.com" rel=3D"noreferrer" target=3D"_blank">esfandiari.m84=
@gmail.com</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=
=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding=
-left:1ex"><div dir=3D"ltr"><a href=3D"https://www.rfc-editor.org/errata_se=
arch.php?rfc=3D3261&amp;eid=3D6793" rel=3D"noreferrer" target=3D"_blank">ht=
tps://www.rfc-editor.org/errata_search.php?rfc=3D3261&amp;eid=3D6793</a></d=
iv><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On =
Wed, Dec 22, 2021 at 1:22 AM Mojtaba Esfandiari.S &lt;<a href=3D"mailto:esf=
andiari.m84@gmail.com" rel=3D"noreferrer" target=3D"_blank">esfandiari.m84@=
gmail.com</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=
=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding=
-left:1ex"><div dir=3D"ltr"><div>Sure,<br></div><div>I have sent my issue t=
o the SIPCore list and also have reported new Errata.</div><div>Thanks</div=
><div>Best Regards.</div><div>Mojtaba<br></div></div><br><div class=3D"gmai=
l_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Tue, Dec 21, 2021 at 11:3=
8 PM Christer Holmberg &lt;<a href=3D"mailto:christer.holmberg@ericsson.com=
" rel=3D"noreferrer" target=3D"_blank">christer.holmberg@ericsson.com</a>&g=
t; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0p=
x 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">





<div lang=3D"FI">
<div><p class=3D"MsoNormal"><span lang=3D"EN-US">Hi Mojtaba,<u></u><u></u><=
/span></p><p class=3D"MsoNormal"><span lang=3D"EN-US"><u></u>=C2=A0<u></u><=
/span></p><p class=3D"MsoNormal"><span lang=3D"EN-US">After an initial thou=
ght, your suggested clarification to section 8.1.1.5 seems correct. It coul=
d perhaps be more generic, though, and e.g.,say that specific procedures ma=
y define rules
 regarding the CSeq value. The 401/407 case could then be mentioned as an e=
xample.<u></u><u></u></span></p><p class=3D"MsoNormal"><span lang=3D"EN-US"=
><u></u>=C2=A0<u></u></span></p><p class=3D"MsoNormal"><span lang=3D"EN-US"=
>In any case, may I suggest that you send your issue to the SIPCORE list?<u=
></u><u></u></span></p><p class=3D"MsoNormal"><span lang=3D"EN-US"><u></u>=
=C2=A0<u></u></span></p><p class=3D"MsoNormal"><span lang=3D"EN-US">Regards=
,<u></u><u></u></span></p><p class=3D"MsoNormal"><span lang=3D"EN-US"><u></=
u>=C2=A0<u></u></span></p><p class=3D"MsoNormal"><span lang=3D"EN-US">Chris=
ter<u></u><u></u></span></p><p class=3D"MsoNormal"><span lang=3D"EN-US"><u>=
</u>=C2=A0<u></u></span></p>
<div style=3D"border-color:rgb(225,225,225) currentcolor currentcolor;borde=
r-style:solid none none;border-width:1pt medium medium;padding:3pt 0cm 0cm"=
><p class=3D"MsoNormal"><b><span lang=3D"EN-US">From:</span></b><span lang=
=3D"EN-US"> sipcore &lt;<a href=3D"mailto:sipcore-bounces@ietf.org" rel=3D"=
noreferrer" target=3D"_blank">sipcore-bounces@ietf.org</a>&gt;
<b>On Behalf Of </b>Mojtaba Esfandiari.S<br>
<b>Sent:</b> tiistai 21. joulukuuta 2021 12.19<br>
<b>To:</b> Liviu Chircu &lt;<a href=3D"mailto:liviu@opensips.org" rel=3D"no=
referrer" target=3D"_blank">liviu@opensips.org</a>&gt;<br>
<b>Cc:</b> <a href=3D"mailto:dispatch@ietf.org" rel=3D"noreferrer" target=
=3D"_blank">dispatch@ietf.org</a>; <a href=3D"mailto:sipcore@ietf.org" rel=
=3D"noreferrer" target=3D"_blank">sipcore@ietf.org</a><br>
<b>Subject:</b> Re: [sipcore] Exception in RFC 3261 document<u></u><u></u><=
/span></p>
</div><p class=3D"MsoNormal"><span lang=3D"EN-US"><u></u>=C2=A0<u></u></spa=
n></p>
<div>
<div><p class=3D"MsoNormal"><span lang=3D"EN-US">Actually, the UE is obeyin=
g the RFC 3261, But the SEMS project is not RFC 3261 compliant.<u></u><u></=
u></span></p>
</div>
<div><p class=3D"MsoNormal"><span lang=3D"EN-US">It occurs because for 401 =
(Unauthorized) or 407 (Proxy Authentication Required) response, the value o=
f CSeq does not change.<u></u><u></u></span></p>
</div>
<div><p class=3D"MsoNormal"><span lang=3D"EN-US">So for more clarity and mo=
re understanding, It would be nice to have a quiet bit of update in RFC 326=
1 section 8.1.1.5.<u></u><u></u></span></p>
</div>
<div><p class=3D"MsoNormal"><span lang=3D"EN-US">For example, the word &quo=
t;arbitrary&quot; in the CSeq value may be confused with the same value as =
before.<u></u><u></u></span></p>
</div>
<div><p class=3D"MsoNormal"><span lang=3D"EN-US">Thanks<u></u><u></u></span=
></p>
</div>
<div><p class=3D"MsoNormal"><span lang=3D"EN-US"><u></u>=C2=A0<u></u></span=
></p>
</div>
</div><p class=3D"MsoNormal"><span lang=3D"EN-US"><u></u>=C2=A0<u></u></spa=
n></p>
<div>
<div><p class=3D"MsoNormal"><span lang=3D"EN-US">On Tue, Dec 21, 2021 at 8:=
25 AM Liviu Chircu &lt;</span><a href=3D"mailto:liviu@opensips.org" rel=3D"=
noreferrer" target=3D"_blank"><span lang=3D"EN-US">liviu@opensips.org</span=
></a><span lang=3D"EN-US">&gt; wrote:<u></u><u></u></span></p>
</div>
<blockquote style=3D"border-color:currentcolor currentcolor currentcolor rg=
b(204,204,204);border-style:none none none solid;border-width:medium medium=
 medium 1pt;padding:0cm 0cm 0cm 6pt;margin:5pt 0cm 5pt 4.8pt"><p class=3D"M=
soNormal" style=3D"margin-bottom:12pt"><span lang=3D"EN-US">On 20.12.2021 2=
3:59, Mojtaba Esfandiari.S wrote:<br>
&gt; The UE sends its request to Sems, then Sems relay the request to <br>
&gt; Asterisk server. because in all INVITE messages, the Sems used the <br=
>
&gt; same CSeq value (CSeq: 10 INVITE), asterisk goes to LOOP for <br>
&gt; authentication UE.<br>
<br>
Then the UE is not RFC 3261-compliant, as it is disobeying the <br>
additional restrictions of =C2=A7 22.2.<br>
<br>
</span>-- <br>
Liviu Chircu<br>
<a href=3D"https://protect2.fireeye.com/v1/url?k=3D31323334-501d5122-313273=
af-454445555731-742427605f27b27a&amp;q=3D1&amp;e=3D15584eeb-52e0-4596-a64d-=
ab25cbbb7dcb&amp;u=3Dhttp%3A%2F%2Fwww.twitter.com%2Fliviuchircu" rel=3D"nor=
eferrer" target=3D"_blank">www.twitter.com/liviuchircu</a> |
<a href=3D"https://protect2.fireeye.com/v1/url?k=3D31323334-501d5122-313273=
af-454445555731-db93e02ae851094d&amp;q=3D1&amp;e=3D15584eeb-52e0-4596-a64d-=
ab25cbbb7dcb&amp;u=3Dhttp%3A%2F%2Fwww.opensips-solutions.com%2F" rel=3D"nor=
eferrer" target=3D"_blank">
www.opensips-solutions.com</a><u></u><u></u></p>
</blockquote>
</div>
</div>
</div>

</blockquote></div>
</blockquote></div>
</blockquote></div>
_______________________________________________<br>sipcore mailing list<br>=
<a href=3D"mailto:sipcore@ietf.org" rel=3D"noreferrer" target=3D"_blank">si=
pcore@ietf.org</a><br><a href=3D"https://www.ietf.org/mailman/listinfo/sipc=
ore" rel=3D"noreferrer" target=3D"_blank">https://www.ietf.org/mailman/list=
info/sipcore</a><br></div></blockquote></div><br></div></div></blockquote><=
/div>
</blockquote></div>

--0000000000007dd45e05d8fb5f3b--

