
From nobody Tue May 18 02:48:45 2021
Return-Path: <wwwrun@rfc-editor.org>
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 220273A1582 for <sipcore@ietfa.amsl.com>; Tue, 18 May 2021 02:48:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=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 KdfanOpz_LKh for <sipcore@ietfa.amsl.com>; Tue, 18 May 2021 02:48:38 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A55003A1578 for <sipcore@ietf.org>; Tue, 18 May 2021 02:48:38 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id CF8E0F407BA; Tue, 18 May 2021 02:48:37 -0700 (PDT)
To: eburger@standardstrack.com, nagdab@gmail.com, superuser@gmail.com, francesca.palombini@ericsson.com, br@brianrosen.net, mahoney@nostrum.com
X-PHP-Originating-Script: 1005:errata_mail_lib.php
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: amrita_ch@yahoo.com, sipcore@ietf.org, rfc-editor@rfc-editor.org
Content-Type: text/plain; charset=UTF-8
Message-Id: <20210518094837.CF8E0F407BA@rfc-editor.org>
Date: Tue, 18 May 2021 02:48:37 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/sipcore/sattjAunJl5Xrit9PwG-eMsJDrE>
Subject: [sipcore] [Technical Errata Reported] RFC8688 (6586)
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: Tue, 18 May 2021 09:48:43 -0000

The following errata report has been submitted for RFC8688,
"A Session Initiation Protocol (SIP) Response Code for Rejected Calls".

--------------------------------------
You may review the report below and at:
https://www.rfc-editor.org/errata/eid6586

--------------------------------------
Type: Technical
Reported by: Amrita Bhatt <amrita_ch@yahoo.com>

Section: 3

Original Text
-------------
                         +--------+         +-----------+
                         | Called |         |   Call    |
        +-----+          | Party  |         | Analytics |   +-----+
        | UAC |          | Proxy  |         |  Engine   |   | UAS |
        +-----+          +--------+         +-----------+   +-----+
           |  INVITE         |                    |            |
           | --------------> |  Is call OK?       |            |
           |                 |------------------->|            |
           |                 |                    |            |
           |                 |               Yes  |            |
           |                 |<-------------------|            |
           |                 |                    |            |
           |                 | INVITE             |            |
           |                 | ------------------------------> |
           |                 |                    |            |
           |                 |                    |       607  |
           |                 | <------------------------------ |
           |                 |                    |            |
           |                 |  Unwanted call     |            |
           |            607  | -----------------> |            |
           | <-------------- |  indicators        |            |
           |                 |                    |            |


Corrected Text
--------------
                         +--------+         +-----------+
                         | Called |         |   Call    |
        +-----+          | Party  |         | Analytics |   +-----+
        | UAC |          | Proxy  |         |  Engine   |   | UAS |
        +-----+          +--------+         +-----------+   +-----+
           |  INVITE         |                    |            |
           | --------------> |  Is call OK?       |            |
           |                 |------------------->|            |
           |                 |                    |            |
           |                 |               No   |            |
           |                 |<-------------------|            |
           |                 |                    |            |
           |                 |              	  |            |
           |                 |                    |            |
           |                 |                    |            |
           |            608  |                    |            |
           | <-------------- |                    |            |
           |                 |                    |            |


Notes
-----
"Figure 4: Rejected (608) Ladder Diagram" does not depict correct signalling flow.

Instructions:
-------------
This erratum is currently posted as "Reported". If necessary, please
use "Reply All" to discuss whether it should be verified or
rejected. When a decision is reached, the verifying party  
can log in to change the status and edit the report, if necessary. 

--------------------------------------
RFC8688 (draft-ietf-sipcore-rejected-09)
--------------------------------------
Title               : A Session Initiation Protocol (SIP) Response Code for Rejected Calls
Publication Date    : December 2019
Author(s)           : E.W. Burger, B. Nagda
Category            : PROPOSED STANDARD
Source              : Session Initiation Protocol Core
Area                : Applications and Real-Time
Stream              : IETF
Verifying Party     : IESG


From nobody Tue May 25 17:32:13 2021
Return-Path: <eburger@standardstrack.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 441373A1589 for <sipcore@ietfa.amsl.com>; Tue, 25 May 2021 17:32:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.088
X-Spam-Level: 
X-Spam-Status: No, score=-1.088 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, SPF_HELO_NONE=0.001, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001, URIBL_SBL=0.5, URIBL_SBL_A=0.1] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=neutral reason="invalid (public key: not available)" header.d=standardstrack.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 v5XRm0wI7vLl for <sipcore@ietfa.amsl.com>; Tue, 25 May 2021 17:32:06 -0700 (PDT)
Received: from se4o-iad1.servconfig.com (se4o-iad1.servconfig.com [199.250.217.18]) (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 4249E3A1583 for <sipcore@ietf.org>; Tue, 25 May 2021 17:32:06 -0700 (PDT)
Received: from biz221.inmotionhosting.com ([192.145.239.201]) by se4-iad1.servconfig.com with esmtps (TLSv1.2:AES128-GCM-SHA256:128) (Exim 4.92) (envelope-from <eburger@standardstrack.com>) id 1llhSg-000Oq9-4m; Tue, 25 May 2021 20:32:02 -0400
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=standardstrack.com; s=default; h=References:To:Cc:In-Reply-To:Date:Subject: Mime-Version:Content-Type:Message-Id:From:Sender:Reply-To: Content-Transfer-Encoding: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=u+Yh+OIIcoTs4OR3NxSq2PCMvS79je21iifZdAsUp3g=; b=f+2AvyyVSYzknFUYGRIXHQTJov +zOqA+qj33iZZ0IVCcqVIVJN3UOZB6sybCvxqoezBK4arMWxsjgbrEdr3kr4fRFoGQa8Z6LPOuqXZ PxPl2YjIQSDa5lu9SYU7P3yhSQML7e8e6Vo/nYZXSuOUXVTiFfv+KqJHMHUneY1b7M70=;
Received: from [68.100.100.136] (port=51613 helo=smtpclient.apple) by biz221.inmotionhosting.com with esmtpsa (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from <eburger@standardstrack.com>) id 1llhSb-00GT3T-KE; Tue, 25 May 2021 17:31:45 -0700
From: Eric Burger <eburger@standardstrack.com>
Message-Id: <22296D26-7DB4-4354-9F7D-3B66ACF302C8@standardstrack.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_8CC44EBC-E3C2-4FCB-A459-068DBAE2A987"; protocol="application/pkcs7-signature"; micalg=sha-256
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.100.0.2.22\))
Date: Tue, 25 May 2021 20:31:44 -0400
In-Reply-To: <20210518094837.CF8E0F407BA@rfc-editor.org>
Cc: Bhavik V Nagda <nagdab@gmail.com>, superuser@gmail.com, francesca.palombini@ericsson.com, Brian Rosen <br@brianrosen.net>, mahoney@nostrum.com, amrita_ch@yahoo.com, sipcore@ietf.org
To: RFC Errata System <rfc-editor@rfc-editor.org>
References: <20210518094837.CF8E0F407BA@rfc-editor.org>
X-Mailer: Apple Mail (2.3654.100.0.2.22)
X-Get-Message-Sender-Via: biz221.inmotionhosting.com: authenticated_id: eburger+standardstrack.com/only user confirmed/virtual account not confirmed
X-Authenticated-Sender: biz221.inmotionhosting.com: eburger@standardstrack.com
X-Originating-IP: 192.145.239.201
X-SpamExperts-Domain: biz221.inmotionhosting.com
X-SpamExperts-Username: 192.145.239.201
Authentication-Results: servconfig.com; auth=pass smtp.auth=192.145.239.201@biz221.inmotionhosting.com
X-SpamExperts-Outgoing-Class: ham
X-SpamExperts-Outgoing-Evidence: Combined (0.17)
X-Recommended-Action: accept
X-Filter-ID: Pt3MvcO5N4iKaDQ5O6lkdGlMVN6RH8bjRMzItlySaT+RGAL+R4Qs0xlVN+ILfIcVPUtbdvnXkggZ 3YnVId/Y5jcf0yeVQAvfjHznO7+bT5y1JMu9hk2W5e6SrIZvOH6vvVm4UDG4QGnnBexGYm3sWKBN e+0GLpPD/lei3mxuh/p02x+raDr28ND8nMrWCyczRF0UPH+c6TbuUqma5R7QOgPmI6JFCLKlvlNz VD4KX6sPKYMfE+V8uoWTTKbjYP+NDThzgMU94s37iQD4iRCUNolFbCszT3E3kdogf/OMyfuj8Amy CX6o5rVm0m4xVtZWHPdj4ZVtaA1ZzJ8YHqJCcr/GW1QOymN5zwCUbhFYnK5JJrEdbXjD+gyEEGSr 8l3jsMbsfPCbm49L3aSnN7qTZyTg127TqHZDxA/kZB41Rh/tZAm5CxZFJFmMJYowSgzgztdnziQq PRIzHM0xZsO3LKGYxI6eAT7BbzeYmkjqtHcKpj5lm4TlcuWQipsxoh6kO4I9/VzTYT7ojR51RkeG yuoo5keMxDDDmZL9OAzJml0F1vLM9cIybVokPLVwNGeGe/AqQm64UwYpIc8nFV5EcoDKd/XBM6Ee MCpZHojmAc8tUSl2WmT0XVwpr4noM18+7rSFKsvvEVZNOj9CknkFzlWgpiRfGOSpo4szFlf4Gpig 4iObGNKAIfyAxmFNRoYowxHqOeBT4r+LJYtXxWC01IjN1dJNyD7+sHaao9ZdwPBUvSqV1F5i8Viy 1vLMOMM2Dzn23lmbQ455+TwtsPDDuZQG7dYoWs1E//3c9tLxiFNewhCVhTPXHcTOo3QHXSGeZw4l bURmFp+QdNYfiyRLYBqZR3KVQgqF/fPYYAfEfsgoE9MMuhnhumpdqkJVxSZqX90QJPyDvvcxEEW2 UWB5dx9biWDiGjilhb5LmNIn2Om7emgr5XPyJxOmzYBSuLMzfzCNg5m9qaFCFMpwiEn7rTRJXT5B R761T1iPG2gBXJ3TPpuFqUUQz+mM8JAD4ECWdyEwLsGpJ0QVlXZ2XSz9LZyLwkuKI51yRR7AImuZ BFyiCb2MlFyJDbr15votsPUsiQHL3fBQQfCPJP/nl3LCdwDm3IkHus1KJdLlVEWX6971R4V/glmb eUNP/Dj/GUP5crDpQppZkgV1Qhx7bWVCV0cuOs2OpHbEsl81ku0Z0CrZBGK35FebR+5cfOOxWc5q jO0zpoeEbpMqYY9OJ1qM0elZegsYJRxHb8DZzi4G5qFoMMMh30z0ou3Uma6ICBqooWDkfaAACQiW MyAesX7/7H247ivQrwCcKDGaVzoLWnJWBRU3XZvUK1+KHvj8p2fa2TUkgk57eJPLGNtJ+TMPvA==
X-Report-Abuse-To: spam@se1-lax1.servconfig.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/sipcore/T2hIqEcuFaXEwb0Aiwt90xyu_Yk>
Subject: Re: [sipcore] [Technical Errata Reported] RFC8688 (6586)
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, 26 May 2021 00:32:11 -0000

--Apple-Mail=_8CC44EBC-E3C2-4FCB-A459-068DBAE2A987
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Good catch! Yet another reason why people need to code to the text and =
not the examples. This is laughably wrong. [I can laugh at myself and =
the entire IESG for not noticing this error.]

Verified.

> On May 18, 2021, at 5:48 AM, RFC Errata System =
<rfc-editor@rfc-editor.org> wrote:
>=20
> The following errata report has been submitted for RFC8688,
> "A Session Initiation Protocol (SIP) Response Code for Rejected =
Calls".
>=20
> --------------------------------------
> You may review the report below and at:
> https://www.rfc-editor.org/errata/eid6586
>=20
> --------------------------------------
> Type: Technical
> Reported by: Amrita Bhatt <amrita_ch@yahoo.com>
>=20
> Section: 3
>=20
> Original Text
> -------------
>                         +--------+         +-----------+
>                         | Called |         |   Call    |
>        +-----+          | Party  |         | Analytics |   +-----+
>        | UAC |          | Proxy  |         |  Engine   |   | UAS |
>        +-----+          +--------+         +-----------+   +-----+
>           |  INVITE         |                    |            |
>           | --------------> |  Is call OK?       |            |
>           |                 |------------------->|            |
>           |                 |                    |            |
>           |                 |               Yes  |            |
>           |                 |<-------------------|            |
>           |                 |                    |            |
>           |                 | INVITE             |            |
>           |                 | ------------------------------> |
>           |                 |                    |            |
>           |                 |                    |       607  |
>           |                 | <------------------------------ |
>           |                 |                    |            |
>           |                 |  Unwanted call     |            |
>           |            607  | -----------------> |            |
>           | <-------------- |  indicators        |            |
>           |                 |                    |            |
>=20
>=20
> Corrected Text
> --------------
>                         +--------+         +-----------+
>                         | Called |         |   Call    |
>        +-----+          | Party  |         | Analytics |   +-----+
>        | UAC |          | Proxy  |         |  Engine   |   | UAS |
>        +-----+          +--------+         +-----------+   +-----+
>           |  INVITE         |                    |            |
>           | --------------> |  Is call OK?       |            |
>           |                 |------------------->|            |
>           |                 |                    |            |
>           |                 |               No   |            |
>           |                 |<-------------------|            |
>           |                 |                    |            |
>           |                 |              	  |            |
>           |                 |                    |            |
>           |                 |                    |            |
>           |            608  |                    |            |
>           | <-------------- |                    |            |
>           |                 |                    |            |
>=20
>=20
> Notes
> -----
> "Figure 4: Rejected (608) Ladder Diagram" does not depict correct =
signalling flow.
>=20
> Instructions:
> -------------
> This erratum is currently posted as "Reported". If necessary, please
> use "Reply All" to discuss whether it should be verified or
> rejected. When a decision is reached, the verifying party =20
> can log in to change the status and edit the report, if necessary.=20
>=20
> --------------------------------------
> RFC8688 (draft-ietf-sipcore-rejected-09)
> --------------------------------------
> Title               : A Session Initiation Protocol (SIP) Response =
Code for Rejected Calls
> Publication Date    : December 2019
> Author(s)           : E.W. Burger, B. Nagda
> Category            : PROPOSED STANDARD
> Source              : Session Initiation Protocol Core
> Area                : Applications and Real-Time
> Stream              : IETF
> Verifying Party     : IESG


--Apple-Mail=_8CC44EBC-E3C2-4FCB-A459-068DBAE2A987
Content-Disposition: attachment;
	filename=smime.p7s
Content-Type: application/pkcs7-signature;
	name=smime.p7s
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExDzANBglghkgBZQMEAgEFADCABgkqhkiG9w0BBwEAAKCCDWMw
ggXuMIID1qADAgECAhArygWunAYXWl021zcEjTcSMA0GCSqGSIb3DQEBCwUAMIGBMQswCQYDVQQG
EwJJVDEQMA4GA1UECAwHQmVyZ2FtbzEZMBcGA1UEBwwQUG9udGUgU2FuIFBpZXRybzEXMBUGA1UE
CgwOQWN0YWxpcyBTLnAuQS4xLDAqBgNVBAMMI0FjdGFsaXMgQ2xpZW50IEF1dGhlbnRpY2F0aW9u
IENBIEczMB4XDTIxMDIxMDIyMDAwOFoXDTIyMDIxMDIyMDAwOFowJTEjMCEGA1UEAwwaZWJ1cmdl
ckBzdGFuZGFyZHN0cmFjay5jb20wggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQDMcNWe
q9iE3KbYf4xzBlv0FPxgP3qEQJpEV3AN69HARESfpD5pbW70OlO8FRjulqxMgfLHB1Oyz4l4jqeh
Pch12NBcPRxvO6GiQijdvlxTWUM2TyhHljz08s63BpULH96WxwNflyD3tanlH8OrGDui8aZosjZ7
28xBD9ebMLSCjZrlecb2RC5l2+9eP7yf5KJZyeVZMJcEheo1Fsna8g6iqwVFIINEDCYAa2cETBwW
OC7FfMDbhfB9G0nNnLztjhj4GVI4CeOxyJGOfDvEGRRw9THKYjlbq3QFC7MS1jowDvgNcfthr9GV
+6U8wMVliGHR6n8+GsNZ0ul6nJisE0lFAgMBAAGjggG7MIIBtzAMBgNVHRMBAf8EAjAAMB8GA1Ud
IwQYMBaAFL6XqaqEv4C/EFN9CTL54S4yG893MH4GCCsGAQUFBwEBBHIwcDA7BggrBgEFBQcwAoYv
aHR0cDovL2NhY2VydC5hY3RhbGlzLml0L2NlcnRzL2FjdGFsaXMtYXV0Y2xpZzMwMQYIKwYBBQUH
MAGGJWh0dHA6Ly9vY3NwMDkuYWN0YWxpcy5pdC9WQS9BVVRIQ0wtRzMwJQYDVR0RBB4wHIEaZWJ1
cmdlckBzdGFuZGFyZHN0cmFjay5jb20wRwYDVR0gBEAwPjA8BgYrgR8BGAEwMjAwBggrBgEFBQcC
ARYkaHR0cHM6Ly93d3cuYWN0YWxpcy5pdC9hcmVhLWRvd25sb2FkMB0GA1UdJQQWMBQGCCsGAQUF
BwMCBggrBgEFBQcDBDBIBgNVHR8EQTA/MD2gO6A5hjdodHRwOi8vY3JsMDkuYWN0YWxpcy5pdC9S
ZXBvc2l0b3J5L0FVVEhDTC1HMy9nZXRMYXN0Q1JMMB0GA1UdDgQWBBRNBlMgm9XWCjywWZrsMv6u
8othBjAOBgNVHQ8BAf8EBAMCBaAwDQYJKoZIhvcNAQELBQADggIBACS3q0GZ+8b/Nv0csvxTyJjn
+hwIrRWLJLAhXiG4Bf3YdNX/KHRiW7pD3RjVFBkcs2xu4vw5WVVLyyMCNjdgLMTSVkllcFWNi7mC
oMZbXzxjqplSbkjn8Ee2NlYWOWa927Tub+If3zfKxc6s9gzXB4S9/rcRYKdI/TKcGWpbW7rsnJVj
lcWOtb8KBxLWodLrya79+gnWA0RDe23nm3rNXdGgmQB9efdssdI1NRpcBimWh0zdvWOmy8GNuvIe
cxdw8Rtzui4PSECr/Njg3ZxMwe5y8M/MtHkJxlHSpxX9+NIzExY4M+5D4UhYCMCKFZfU8gU+8PZD
4WQdEfyTfq7+298ICjiA8fgQR/1JsAmsSULXXWLOuLMypCTLBdvFttR+uNvb03iFRpea/enuOs1U
Nun3/3hrNpF5ZP1189r/ovrJDOK0m/UthZU8UCGONXNYu/GfWyLlEn4/FMMaxujSl8GH/ADT2dmT
bJyWhR1Owic1KRH0shwgKTEJ9svF7Dxk1XTb2jPjvio+SdFo9GRXF3+K6+v32H+o3wAxekMZMTwh
oFjz8cfOrnQ0B6kU6S78Cxus5f7EGmLANbJ/pMncGD/1L/KBS3DetCZQgohcm5CpDg7MX/p3ZDvu
h5ijazZ49h282356WQIUoviuXH9mjkynvyh+VJR1dUDZNmpfKfMXMIIHbTCCBVWgAwIBAgIQFxA+
3j2KHLXKBlGT58pDazANBgkqhkiG9w0BAQsFADBrMQswCQYDVQQGEwJJVDEOMAwGA1UEBwwFTWls
YW4xIzAhBgNVBAoMGkFjdGFsaXMgUy5wLkEuLzAzMzU4NTIwOTY3MScwJQYDVQQDDB5BY3RhbGlz
IEF1dGhlbnRpY2F0aW9uIFJvb3QgQ0EwHhcNMjAwNzA2MDg0NTQ3WhcNMzAwOTIyMTEyMjAyWjCB
gTELMAkGA1UEBhMCSVQxEDAOBgNVBAgMB0JlcmdhbW8xGTAXBgNVBAcMEFBvbnRlIFNhbiBQaWV0
cm8xFzAVBgNVBAoMDkFjdGFsaXMgUy5wLkEuMSwwKgYDVQQDDCNBY3RhbGlzIENsaWVudCBBdXRo
ZW50aWNhdGlvbiBDQSBHMzCCAiIwDQYJKoZIhvcNAQEBBQADggIPADCCAgoCggIBAO3mh5ahwaS2
7cJCVfc/Dw8iYF8T4KZDiIZJkXkcGy8aUA/cRgHu9ro6hsxRYe/ED4AIcSlarRh82HqtFSVQs4Zw
ikQW1V/icCIS91C2IVAGa1YlKfedqgweqky+bBniUvRevVT0keZOqRTcO5hw007dL6FhYNmlZBt5
IaJs1V6IniRjokOHR++qWgrUGy5LefY6ACs9gZ8Bi0OMK9PZ37pibeQCsdmMRytl4Ej7JVWeM/Bt
NIIprHwO1LY0/8InpGOmdG+5LC6xHLzg53B0HvVUqzUQNePUhNwJZFmmTP46FXovxmH4/SuY5IkX
op0eJqjN+dxRHHizngYUk1EaTHUOcLFy4vQ0kxgbjb+GsNg6M2/6gZZIRk78JPdpotIwHnBNtkp9
wPVH61NqdcP7kbPkyLXkNMTtAfydpmNnGqqHLEvUrK4iBpUPG9C09KOjm9OyhrT2uf5SLzJsee9g
79r/rw4hAgcsZtR3YI6fCbROJncmD+hgbHCck+9TWcNc1x5xZMgm8UXmoPamkkfceAlVV49QQ5jU
TgqneTQHyF1F2ExXmf47pEIoJMVxloRIXywQuB2uqcIs8/X6tfsMDynFmhfT/0mTrgQ6xt9DIsgm
WuuhvZhLReWS7oeKxnyqscuGeTMXnLs7fjGZq0inyhnlznhA/4rl+WdNjNaO4jEvAgMBAAGjggH0
MIIB8DAPBgNVHRMBAf8EBTADAQH/MB8GA1UdIwQYMBaAFFLYiDrIn3hm7YnzezhwlMkCAjbQMEEG
CCsGAQUFBwEBBDUwMzAxBggrBgEFBQcwAYYlaHR0cDovL29jc3AwNS5hY3RhbGlzLml0L1ZBL0FV
VEgtUk9PVDBFBgNVHSAEPjA8MDoGBFUdIAAwMjAwBggrBgEFBQcCARYkaHR0cHM6Ly93d3cuYWN0
YWxpcy5pdC9hcmVhLWRvd25sb2FkMB0GA1UdJQQWMBQGCCsGAQUFBwMCBggrBgEFBQcDBDCB4wYD
VR0fBIHbMIHYMIGWoIGToIGQhoGNbGRhcDovL2xkYXAwNS5hY3RhbGlzLml0L2NuJTNkQWN0YWxp
cyUyMEF1dGhlbnRpY2F0aW9uJTIwUm9vdCUyMENBLG8lM2RBY3RhbGlzJTIwUy5wLkEuJTJmMDMz
NTg1MjA5NjcsYyUzZElUP2NlcnRpZmljYXRlUmV2b2NhdGlvbkxpc3Q7YmluYXJ5MD2gO6A5hjdo
dHRwOi8vY3JsMDUuYWN0YWxpcy5pdC9SZXBvc2l0b3J5L0FVVEgtUk9PVC9nZXRMYXN0Q1JMMB0G
A1UdDgQWBBS+l6mqhL+AvxBTfQky+eEuMhvPdzAOBgNVHQ8BAf8EBAMCAQYwDQYJKoZIhvcNAQEL
BQADggIBACab5xtZDXSzEgPp51X3hICFzULDO2EcV8em5hLfSCKxZR9amCnjcODVfMbaKfdUZXte
vMIIZmHgkz9dBan7ijGbJXjZCPP29zwZGSyCjpfadg5s9hnNCN1r3DGwIHfyLgbcfffDyV/2wW+X
TGbhldnazZsX892q+srRmC8XnX4ygg+eWL/AkHDenvbFuTlJvUyd5I7e1nb3dYXMObPu24ZTQ9/K
1hSQbs7pqecaptTUjoIDpBUpSp4Us+h1I4MAWonemKYoPS9f0y65JrRCKcfsKSI+1kwPSanDDMiy
dKzeo46XrS0hlA5NzQjqUJ7UsuGvPtDvknqc0v03nNXBnUjejYtvwO3sEDXdUW5m9kjNqlQZXzdH
umZJVqPUGKTWcn9Hf3d7qbCmmxPXjQoNUuHg56fLCanZWkEO4SP1GAgIA7SyJu/yffv0ts7sBFrS
TD3L2mCAXM3Y8BfblvvDSf2bvySm/fPe9brmuzrCXsTxUQc1+/z5ydvzV3E3cLnUoSXP6XfXNyEV
O6sPkcUSnISHM798xLkCTB5EkjPCjPE2zs4v9L9JVOkkskvW6RnWWccdfR3fELNHL/kep8re6Ibb
Ys8Hn5GM0Ohs8CMDPYEox+QX/6/SnOfyaqqSilBonMQBstsymBBgdEKO+tTHHCMnJQVvZn7jRQ20
wXgxMrvNMYIDhTCCA4ECAQEwgZYwgYExCzAJBgNVBAYTAklUMRAwDgYDVQQIDAdCZXJnYW1vMRkw
FwYDVQQHDBBQb250ZSBTYW4gUGlldHJvMRcwFQYDVQQKDA5BY3RhbGlzIFMucC5BLjEsMCoGA1UE
AwwjQWN0YWxpcyBDbGllbnQgQXV0aGVudGljYXRpb24gQ0EgRzMCECvKBa6cBhdaXTbXNwSNNxIw
DQYJYIZIAWUDBAIBBQCgggG/MBgGCSqGSIb3DQEJAzELBgkqhkiG9w0BBwEwHAYJKoZIhvcNAQkF
MQ8XDTIxMDUyNjAwMzE0NFowLwYJKoZIhvcNAQkEMSIEINbekiuNGKyGl2cqKRO8Z/j7lIXehq47
2b9T0Ky59uehMIGnBgkrBgEEAYI3EAQxgZkwgZYwgYExCzAJBgNVBAYTAklUMRAwDgYDVQQIDAdC
ZXJnYW1vMRkwFwYDVQQHDBBQb250ZSBTYW4gUGlldHJvMRcwFQYDVQQKDA5BY3RhbGlzIFMucC5B
LjEsMCoGA1UEAwwjQWN0YWxpcyBDbGllbnQgQXV0aGVudGljYXRpb24gQ0EgRzMCECvKBa6cBhda
XTbXNwSNNxIwgakGCyqGSIb3DQEJEAILMYGZoIGWMIGBMQswCQYDVQQGEwJJVDEQMA4GA1UECAwH
QmVyZ2FtbzEZMBcGA1UEBwwQUG9udGUgU2FuIFBpZXRybzEXMBUGA1UECgwOQWN0YWxpcyBTLnAu
QS4xLDAqBgNVBAMMI0FjdGFsaXMgQ2xpZW50IEF1dGhlbnRpY2F0aW9uIENBIEczAhArygWunAYX
Wl021zcEjTcSMA0GCSqGSIb3DQEBCwUABIIBAEIRoDSlBMrY9CCklCYaIrbkUmRdSbaFkGUcohoa
cUmpOVelHTJRmdAkd5wwdA1KN2J7G8mq0lyJVQg+kRWtHWMaCMNuYaZsF+I73YI2EE8Je1nV2e0I
m91xgiZuty34vvlh6akF1eR7SEbOOEkQCAe9/aQwVSXMKpXo+hXgg8kVr3FWL5NWR77xHpqhLbNB
obUK+XN48WK8e8ePgnpaqQTadZ7/UGTXTliGlh/delc26pKXVGMwTH37PbRNo0VLFINGGDj145XX
rkhQ3VGXRPIU3ilYyZ+XsqJPkW3cbxU4eVO0JzTHlf77TzoR0BSHItvZp/2atmbkFsiEwGBzCIQA
AAAAAAA=
--Apple-Mail=_8CC44EBC-E3C2-4FCB-A459-068DBAE2A987--


From hoil.choi@hotmail.com  Fri May 28 00:08:41 2021
Return-Path: <hoil.choi@hotmail.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 24C613A1DC7 for <sipcore@ietfa.amsl.com>; Fri, 28 May 2021 00:08:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.1
X-Spam-Level: 
X-Spam-Status: No, score=-2.1 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_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-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=hotmail.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 ngheNUxUZkZM for <sipcore@ietfa.amsl.com>; Fri, 28 May 2021 00:08:35 -0700 (PDT)
Received: from NAM10-DM6-obe.outbound.protection.outlook.com (mail-dm6nam10olkn2030.outbound.protection.outlook.com [40.92.41.30]) (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 0113B3A1DCE for <sipcore@ietf.org>; Fri, 28 May 2021 00:08:34 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=bSaQ/U9PpfDlSORFqylQ6hPU/ZbAwBszR5whV/Yvpa1Wks9DyvR0HrbLHEFGGZkxwbe5w0IpqJxenCGW+KIsQ1C/vYuuAtNRdcuPpYqBorZvXxkNuNgtm8G+fAxQMA9XsAdLpTU/QKrlbVC313UiY/jjICthcUZo1y+NFupNmfc1wke/tVlQBB3e2bOLZzJmfbCD1lXFclnrvKfxriVKK1xqGwS6qzJyvStgTHcMCXn4s2YtdjFrYEtKplikzgXjzYoOCi8A6cPBxBB1Xvs9tpoRO6pg0rYWD76UDeOovzlfblYlwyybb6rd2lAVijT4bo3MS7OCc4sJxcFrklMM/g==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;  s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=yFsflWaUZ5G2DznOMyZzzCiYD4ZLblbG+FcVUBN+vSw=; b=OhEWGlXVFs7AItb0Qb0+ImLS63Gn/J7dgT1uZQGlRXFRI6DPJhWdYw3x/CCjxt08/Yjav3etFVMmqx03VJcSP1Z5pnVoXnrsOwcQZR0tojD2MUWNl+FmZ73NOv66VmMkWY1hwNlCcjlSq5OVrmu4wRMyldkXh56AMykDbjphJMT5frQrpFpMalcKw2Tneseacl0yZ4XSqZtPFNBV2u9Zc/nfcX4N6oaX+0mYbla+08SEJICZ+U+/SSG9XqsZgq8blEiP2hFKl/TVDkxtzUxWKGosHhbHN5clXtzVFSyFl9r2iu8BdxEAN5TLHdQiGhdfIHVgoduuNvUBkuyKK2877Q==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=none; dmarc=none; dkim=none; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hotmail.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=yFsflWaUZ5G2DznOMyZzzCiYD4ZLblbG+FcVUBN+vSw=; b=bdlVgB046jauFdLT91iL/79QLHKhAYSTmLymVofkDqyubfzQY5ZUgXQTPBd84pPsIB1L5IIWrULQyHSUpfJGW+AmANcGTbKHklocTCltKKq9IZTJRexwu98vEUEvZ60tGi/2WBh5DElzvUaZj7z0PQrTWA5Jf5E+F6Mk+2tWB+AFy8EPL3Up4KdQM5luN9XKicJjYvsrsgRyBogHmjSOZFRIoTjxk8wsdiOh0d6LdJlc3W2bOJsnNE+sG5AE8ynXg+9Q1nXh+kTD6tuQP08+vqfrHu0T9aziU5msio/h1S9PrBCJQ0tP7DiXZWw4rsc+VBsiwkd9YKrZ2XF5Sc0fBw==
Received: from DM6NAM10FT014.eop-nam10.prod.protection.outlook.com (2a01:111:e400:7e86::4c) by DM6NAM10HT210.eop-nam10.prod.protection.outlook.com (2a01:111:e400:7e86::135) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.4150.28; Fri, 28 May 2021 07:08:33 +0000
Received: from CO6PR02MB7603.namprd02.prod.outlook.com (2a01:111:e400:7e86::49) by DM6NAM10FT014.mail.protection.outlook.com (2a01:111:e400:7e86::281) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.4150.28 via Frontend Transport; Fri, 28 May 2021 07:08:33 +0000
Received: from CO6PR02MB7603.namprd02.prod.outlook.com ([fe80::11c6:9a98:84a:7f22]) by CO6PR02MB7603.namprd02.prod.outlook.com ([fe80::11c6:9a98:84a:7f22%7]) with mapi id 15.20.4173.021; Fri, 28 May 2021 07:08:33 +0000
From: Hoil Choi <hoil.choi@hotmail.com>
To: "sipcore@ietf.org" <sipcore@ietf.org>
Thread-Topic: RFC 4028 UAS behavior requirement of Require header
Thread-Index: AQHXU42WCj5aHc4bTkuBkpJKe+ECaA==
Date: Fri, 28 May 2021 07:08:32 +0000
Message-ID: <CO6PR02MB7603DC7C115904E3A41C9A95EE229@CO6PR02MB7603.namprd02.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-incomingtopheadermarker: OriginalChecksum:18E37EF30986DB0A37C53FE76329C9352079974215C7CFDE9B03BC871F75C9DA; UpperCasedChecksum:8CB5BE63DA5CD057F85CE4BAC07D2A9DA9C5BFCE9F939F6A66C9DDF0EE23D894; SizeAsReceived:6652; Count:41
x-tmn: [VVpEuKcE8k3GO3GBQVpY6AAK9KVssMt7]
x-ms-publictraffictype: Email
x-incomingheadercount: 41
x-eopattributedmessage: 0
x-ms-office365-filtering-correlation-id: a360bbc6-ce86-459d-8eb7-08d921a76794
x-ms-traffictypediagnostic: DM6NAM10HT210:
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: r6TQqpbzoFBWW1L2cMcF6Rd3/EfTDKPEgWQiqXqszwzQxmuywWGeDILAy1rf0DGdPQMcDeS7Q4UoFT+eXkcr1SDk22WCeuI4OMAUiRweKYH8CCTWYlLrc+qHVyqkMw84I5hiAIzSPS7a5DTnWUojV9tJm3V+otq9phcjBSVyo3Hz0wPwBLjBktNBjeJpQpxk7gQAzu0D753yWUOduACD4jQ8dE5TCBkeUcRyKKxzAqGOg8l+N59qzc+S9gDUcdQ85PC7TRuk2g7Ka1FhzkB02Li8KBFkGhkpTIIp+Ppj/W3+EVnJxm0QveOv00iqquGPiuL6R/Yr608gu8lVJpe1vUhveZ+9IMbI2W9pWvKBZetrfWsoJX80lcqB573gnHTl/nDJoOMH4aWJAuAIvj7+FA==
x-ms-exchange-antispam-messagedata: J1wRYE97fYmLHWXRISVH7cBLGdHtvG2uuq0vLJK1UEqH5Fitv0iyGF5N4MtzHSnBkKZiwkIhCgBmNOwGgIF86hMG+At6gbypvprhSibKak7F00zWyekWuE/WvQ3IaWfRrQ7qFbzmKj66SoMxtec/PA==
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_CO6PR02MB7603DC7C115904E3A41C9A95EE229CO6PR02MB7603namp_"
MIME-Version: 1.0
X-OriginatorOrg: hotmail.com
X-MS-Exchange-CrossTenant-AuthAs: Anonymous
X-MS-Exchange-CrossTenant-AuthSource: DM6NAM10FT014.eop-nam10.prod.protection.outlook.com
X-MS-Exchange-CrossTenant-RMS-PersistedConsumerOrg: 00000000-0000-0000-0000-000000000000
X-MS-Exchange-CrossTenant-Network-Message-Id: a360bbc6-ce86-459d-8eb7-08d921a76794
X-MS-Exchange-CrossTenant-originalarrivaltime: 28 May 2021 07:08:32.9943 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Internet
X-MS-Exchange-CrossTenant-id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa
X-MS-Exchange-CrossTenant-rms-persistedconsumerorg: 00000000-0000-0000-0000-000000000000
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM6NAM10HT210
Archived-At: <https://mailarchive.ietf.org/arch/msg/sipcore/P_nEnqp8ZcxNdZSscbn4hI-R0yY>
X-Mailman-Approved-At: Fri, 28 May 2021 08:02:06 -0700
Subject: [sipcore] RFC 4028 UAS behavior requirement of Require header
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: Fri, 28 May 2021 07:14:51 -0000

--_000_CO6PR02MB7603DC7C115904E3A41C9A95EE229CO6PR02MB7603namp_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hello,

I hope this mail finds appropriate person or team for an answer to my quest=
ion on RFC 4028.
I am a SIP enthusiast and always learning a lot about it, but by no means a=
m I an expert; so please excuse my ignorance.

I came across an interesting statement In Section 9 UAS Behavior (or page 1=
6).


If the refresher parameter in the Session-Expires header field in the
   2xx response has a value of 'uac', the UAS MUST place a Require
   header field into the response with the value 'timer'.

Statement seems to convey that UAS must place a Require header with value '=
timer' when UAC requests itself to be the refresher.

However, this statement should only be true, if UAC did not put Session-Exp=
ire with value of 'uac'.

If UAC, in INVITE request, put Session-Expire with value of 'uac' (itself),=
 UAS should not bother putting Require header field in the response.  Or to=
 be more accurate, UAC should include 'timer' in Supported header, so that =
UAS doesn't have to bother putting Require header field.

What is the reason behind the requirement of Require header, from UAS in th=
is case?

Thanks!
Hoil Choi
253-273-5442


--_000_CO6PR02MB7603DC7C115904E3A41C9A95EE229CO6PR02MB7603namp_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-=
1">
<style type=3D"text/css" style=3D"display:none;"> P {margin-top:0;margin-bo=
ttom:0;} </style>
</head>
<body dir=3D"ltr">
<div style=3D"font-family: Calibri, Helvetica, sans-serif; font-size: 12pt;=
 color: rgb(0, 0, 0);">
Hello,&nbsp;</div>
<div style=3D"font-family: Calibri, Helvetica, sans-serif; font-size: 12pt;=
 color: rgb(0, 0, 0);">
<br>
</div>
<div style=3D"font-family: Calibri, Helvetica, sans-serif; font-size: 12pt;=
 color: rgb(0, 0, 0);">
I hope this mail finds appropriate person or team for an answer to my quest=
ion on RFC 4028.&nbsp;</div>
<div style=3D"font-family: Calibri, Helvetica, sans-serif; font-size: 12pt;=
 color: rgb(0, 0, 0);">
I am a SIP enthusiast and always learning a lot about it, but by no means a=
m I an expert; so please excuse my ignorance. &nbsp;</div>
<div style=3D"font-family: Calibri, Helvetica, sans-serif; font-size: 12pt;=
 color: rgb(0, 0, 0);">
<br>
</div>
<div style=3D"font-family: Calibri, Helvetica, sans-serif; font-size: 12pt;=
 color: rgb(0, 0, 0);">
I came across an interesting statement In Section 9 UAS Behavior (or page 1=
6).</div>
<div style=3D"font-family: Calibri, Helvetica, sans-serif; font-size: 12pt;=
 color: rgb(0, 0, 0);">
<pre class=3D"newpage" style=3D"font-weight:400;font-size:13.3333px;margin-=
top:0px;margin-bottom:0px;break-before:page;orphans:2;widows:2"><br></pre>
<pre class=3D"newpage" style=3D"font-weight:400;font-size:13.3333px;margin-=
top:0px;margin-bottom:0px;break-before:page;orphans:2;widows:2">If the refr=
esher parameter in the Session-Expires header field in the=0A=
&nbsp; &nbsp;2xx response has a value of 'uac', the UAS MUST place a Requir=
e=0A=
&nbsp; &nbsp;header field into the response with the value 'timer'. </pre>
<br>
</div>
<div style=3D"font-family: Calibri, Helvetica, sans-serif; font-size: 12pt;=
 color: rgb(0, 0, 0);">
Statement seems to convey that UAS must place a Require header with value '=
timer' when UAC requests itself to be the refresher. &nbsp;</div>
<div style=3D"font-family: Calibri, Helvetica, sans-serif; font-size: 12pt;=
 color: rgb(0, 0, 0);">
<br>
</div>
<div style=3D"font-family: Calibri, Helvetica, sans-serif; font-size: 12pt;=
 color: rgb(0, 0, 0);">
However, this statement should only be true, if UAC did not put Session-Exp=
ire with value of 'uac'. &nbsp;</div>
<div style=3D"font-family: Calibri, Helvetica, sans-serif; font-size: 12pt;=
 color: rgb(0, 0, 0);">
<br>
</div>
<div style=3D"font-family: Calibri, Helvetica, sans-serif; font-size: 12pt;=
 color: rgb(0, 0, 0);">
If UAC, in INVITE request, put Session-Expire with value of 'uac' (itself),=
 UAS should not bother putting Require header field in the response. &nbsp;=
Or to be more accurate, UAC should include 'timer' in Supported header, so =
that UAS doesn't have to bother putting
 Require header field. &nbsp;</div>
<div style=3D"font-family: Calibri, Helvetica, sans-serif; font-size: 12pt;=
 color: rgb(0, 0, 0);">
<br>
</div>
<div style=3D"font-family: Calibri, Helvetica, sans-serif; font-size: 12pt;=
 color: rgb(0, 0, 0);">
What is the reason behind the requirement of Require header, from UAS in th=
is case?</div>
<div style=3D"font-family: Calibri, Helvetica, sans-serif; font-size: 12pt;=
 color: rgb(0, 0, 0);">
<br>
</div>
<div style=3D"font-family: Calibri, Helvetica, sans-serif; font-size: 12pt;=
 color: rgb(0, 0, 0);">
Thanks!</div>
<div style=3D"font-family: Calibri, Helvetica, sans-serif; font-size: 12pt;=
 color: rgb(0, 0, 0);">
Hoil Choi</div>
<div style=3D"font-family: Calibri, Helvetica, sans-serif; font-size: 12pt;=
 color: rgb(0, 0, 0);">
253-273-5442</div>
<div style=3D"font-family: Calibri, Helvetica, sans-serif; font-size: 12pt;=
 color: rgb(0, 0, 0);">
<br>
</div>
</body>
</html>

--_000_CO6PR02MB7603DC7C115904E3A41C9A95EE229CO6PR02MB7603namp_--


From nobody Fri May 28 08:57:19 2021
Return-Path: <br@brianrosen.net>
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 9468E3A2CC8 for <sipcore@ietfa.amsl.com>; Fri, 28 May 2021 08:57:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.887
X-Spam-Level: 
X-Spam-Status: No, score=-1.887 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, T_SPF_PERMERROR=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=brianrosen-net.20150623.gappssmtp.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 SbotpqplQXda for <sipcore@ietfa.amsl.com>; Fri, 28 May 2021 08:57:13 -0700 (PDT)
Received: from mail-il1-x12e.google.com (mail-il1-x12e.google.com [IPv6:2607:f8b0:4864:20::12e]) (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 485DB3A2C8F for <sipcore@ietf.org>; Fri, 28 May 2021 08:57:13 -0700 (PDT)
Received: by mail-il1-x12e.google.com with SMTP id h15so3730589ilr.2 for <sipcore@ietf.org>; Fri, 28 May 2021 08:57:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=brianrosen-net.20150623.gappssmtp.com; s=20150623; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=C4iknmHWL0ZOvSlIade87fWBdEw+u1H/4bvRQXOm4/s=; b=ukfAP+sCvYrhXiuAgJ6Hi1DKXVRBjyqJMK/0VmKoZyT2nlfHj6DIX61RsB5uEyWMLM EyFPoNW5Bw0/i5Bfwu1fWQPcPu6PMsEQz54npvXkWKTmVmQnYmPecrv8/MwTLunOwTRx vPbXeF0+ruVWSSCk0NS8Tp6yX32j7Bnpy8LNUMUj46wqbVwf5PtBwsRkuHOQ68kb+mjR GBvhw42eGb9loyHh7lLunmzOKjI9wpCaHskAM8KMEn1nOiyAOBUnG++tEeb24A48xxxv lszYJozk103F+8yniHTl8BDOv3TFnKr9MBJhyySvsw97MbYgr0h6nQ7eF6d1RWfbXOmo BJSA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=C4iknmHWL0ZOvSlIade87fWBdEw+u1H/4bvRQXOm4/s=; b=nIxjHtTEW5WtZVUeXBuBve2cwKur/1ZlNF4F27tUJ6origmt8JPBU4rPhe5rlHui40 sZPCjtqSsPYV26aVJK/3b29i9n+W6WOkYqZHaN0JLyDfeF177qb/sIQTvfeFNJ2hn6kO 31s49yfXw1LNAlaK+W66gtr7w6PwpgDdF0rKoM7rWPIiGuNud+18NaoyPEDyU/x3CO9e FMgN77zS/TtqNiZdP1ACO534+OOmYRrC9ENsbOX/NjzqO21FpN7p+5UdoNZCAJiH3qBP ofzzxnzxgb4nFdik2104avFrizavvuM9k6UhzW/ZpmF9gjQCPPwx41fYzPbVC4cwYl3J NDWA==
X-Gm-Message-State: AOAM532ZtvZnrEyIGVKJOtsjKXnbxpK1T0eVV+hJrLDDdbodYTMXmair siGmLyK78Kq2YxSvg/h8oS2+bg==
X-Google-Smtp-Source: ABdhPJzk1FkYCDj+KNqS567Xp6X6c9sVWKEn7XypKqQ/6Ofd3eG902W07e0klTq0KmaBDUnX7sVn7w==
X-Received: by 2002:a92:6c0f:: with SMTP id h15mr7506584ilc.19.1622217431961;  Fri, 28 May 2021 08:57:11 -0700 (PDT)
Received: from brians-mbp.lan (dynamic-acs-24-154-121-237.zoominternet.net. [24.154.121.237]) by smtp.gmail.com with ESMTPSA id w6sm3115803ilu.47.2021.05.28.08.57.11 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Fri, 28 May 2021 08:57:11 -0700 (PDT)
From: Brian Rosen <br@brianrosen.net>
Message-Id: <80EE14E6-AF9B-4042-A397-FE359AB040C7@brianrosen.net>
Content-Type: multipart/alternative; boundary="Apple-Mail=_30CFEED2-23DF-4AAF-A125-146F9A346D5B"
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.60.0.2.21\))
Date: Fri, 28 May 2021 11:57:10 -0400
In-Reply-To: <CO6PR02MB7603DC7C115904E3A41C9A95EE229@CO6PR02MB7603.namprd02.prod.outlook.com>
Cc: "sipcore@ietf.org" <sipcore@ietf.org>
To: Hoil Choi <hoil.choi@hotmail.com>
References: <CO6PR02MB7603DC7C115904E3A41C9A95EE229@CO6PR02MB7603.namprd02.prod.outlook.com>
X-Mailer: Apple Mail (2.3654.60.0.2.21)
Archived-At: <https://mailarchive.ietf.org/arch/msg/sipcore/Z963LpCwDnbQMOrRYPHoOUxmkDc>
Subject: Re: [sipcore] RFC 4028 UAS behavior requirement of Require header
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: Fri, 28 May 2021 15:57:18 -0000

--Apple-Mail=_30CFEED2-23DF-4AAF-A125-146F9A346D5B
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

You should send this message to the sip-implementors list: =
sip-implementors@lists.cs.columbia.edu
https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors =
<https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors>

> On May 28, 2021, at 3:08 AM, Hoil Choi <hoil.choi@hotmail.com> wrote:
>=20
> Hello,=20
>=20
> I hope this mail finds appropriate person or team for an answer to my =
question on RFC 4028.=20
> I am a SIP enthusiast and always learning a lot about it, but by no =
means am I an expert; so please excuse my ignorance. =20
>=20
> I came across an interesting statement In Section 9 UAS Behavior (or =
page 16).
>=20
> If the refresher parameter in the Session-Expires header field in the
>    2xx response has a value of 'uac', the UAS MUST place a Require
>    header field into the response with the value 'timer'.=20
>=20
> Statement seems to convey that UAS must place a Require header with =
value 'timer' when UAC requests itself to be the refresher. =20
>=20
> However, this statement should only be true, if UAC did not put =
Session-Expire with value of 'uac'. =20
>=20
> If UAC, in INVITE request, put Session-Expire with value of 'uac' =
(itself), UAS should not bother putting Require header field in the =
response.  Or to be more accurate, UAC should include 'timer' in =
Supported header, so that UAS doesn't have to bother putting Require =
header field. =20
>=20
> What is the reason behind the requirement of Require header, from UAS =
in this case?
>=20
> Thanks!
> Hoil Choi
> 253-273-5442
>=20
> _______________________________________________
> sipcore mailing list
> sipcore@ietf.org <mailto:sipcore@ietf.org>
> https://www.ietf.org/mailman/listinfo/sipcore =
<https://www.ietf.org/mailman/listinfo/sipcore>

--Apple-Mail=_30CFEED2-23DF-4AAF-A125-146F9A346D5B
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html; =
charset=3Dus-ascii"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; line-break: after-white-space;" class=3D"">You =
should send this message to the sip-implementors list:&nbsp;<a =
href=3D"mailto:sip-implementors@lists.cs.columbia.edu" =
class=3D"">sip-implementors@lists.cs.columbia.edu</a><div class=3D""><a =
href=3D"https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors" =
class=3D"">https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors=
</a><br class=3D""><div><br class=3D""><blockquote type=3D"cite" =
class=3D""><div class=3D"">On May 28, 2021, at 3:08 AM, Hoil Choi &lt;<a =
href=3D"mailto:hoil.choi@hotmail.com" =
class=3D"">hoil.choi@hotmail.com</a>&gt; wrote:</div><br =
class=3D"Apple-interchange-newline"><div class=3D""><meta =
charset=3D"UTF-8" class=3D""><div style=3D"font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none; font-family: Calibri, Helvetica, sans-serif; =
font-size: 12pt;" class=3D"">Hello,&nbsp;</div><div style=3D"font-style: =
normal; font-variant-caps: normal; font-weight: normal; letter-spacing: =
normal; text-align: start; text-indent: 0px; text-transform: none; =
white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none; font-family: Calibri, Helvetica, sans-serif; =
font-size: 12pt;" class=3D""><br class=3D""></div><div =
style=3D"font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none; font-family: =
Calibri, Helvetica, sans-serif; font-size: 12pt;" class=3D"">I hope this =
mail finds appropriate person or team for an answer to my question on =
RFC 4028.&nbsp;</div><div style=3D"font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none; font-family: Calibri, Helvetica, sans-serif; =
font-size: 12pt;" class=3D"">I am a SIP enthusiast and always learning a =
lot about it, but by no means am I an expert; so please excuse my =
ignorance. &nbsp;</div><div style=3D"font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none; font-family: Calibri, Helvetica, sans-serif; =
font-size: 12pt;" class=3D""><br class=3D""></div><div =
style=3D"font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none; font-family: =
Calibri, Helvetica, sans-serif; font-size: 12pt;" class=3D"">I came =
across an interesting statement In Section 9 UAS Behavior (or page =
16).</div><div style=3D"font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none; font-family: Calibri, Helvetica, sans-serif; font-size: 12pt;" =
class=3D""><pre class=3D"newpage" style=3D"font-weight: 400; font-size: =
13.3333px; margin-top: 0px; margin-bottom: 0px; break-before: page; =
orphans: 2; widows: 2;"><br class=3D""></pre><pre class=3D"newpage" =
style=3D"font-weight: 400; font-size: 13.3333px; margin-top: 0px; =
margin-bottom: 0px; break-before: page; orphans: 2; widows: 2;">If the =
refresher parameter in the Session-Expires header field in the
&nbsp; &nbsp;2xx response has a value of 'uac', the UAS MUST place a =
Require
&nbsp; &nbsp;header field into the response with the value 'timer'. =
</pre><br class=3D""></div><div style=3D"font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none; font-family: Calibri, Helvetica, sans-serif; =
font-size: 12pt;" class=3D"">Statement seems to convey that UAS must =
place a Require header with value 'timer' when UAC requests itself to be =
the refresher. &nbsp;</div><div style=3D"font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none; font-family: Calibri, Helvetica, sans-serif; =
font-size: 12pt;" class=3D""><br class=3D""></div><div =
style=3D"font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none; font-family: =
Calibri, Helvetica, sans-serif; font-size: 12pt;" class=3D"">However, =
this statement should only be true, if UAC did not put Session-Expire =
with value of 'uac'. &nbsp;</div><div style=3D"font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none; font-family: Calibri, Helvetica, sans-serif; =
font-size: 12pt;" class=3D""><br class=3D""></div><div =
style=3D"font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none; font-family: =
Calibri, Helvetica, sans-serif; font-size: 12pt;" class=3D"">If UAC, in =
INVITE request, put Session-Expire with value of 'uac' (itself), UAS =
should not bother putting Require header field in the response. &nbsp;Or =
to be more accurate, UAC should include 'timer' in Supported header, so =
that UAS doesn't have to bother putting Require header field. =
&nbsp;</div><div style=3D"font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none; font-family: Calibri, Helvetica, sans-serif; font-size: 12pt;" =
class=3D""><br class=3D""></div><div style=3D"font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none; font-family: Calibri, Helvetica, sans-serif; =
font-size: 12pt;" class=3D"">What is the reason behind the requirement =
of Require header, from UAS in this case?</div><div style=3D"font-style: =
normal; font-variant-caps: normal; font-weight: normal; letter-spacing: =
normal; text-align: start; text-indent: 0px; text-transform: none; =
white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none; font-family: Calibri, Helvetica, sans-serif; =
font-size: 12pt;" class=3D""><br class=3D""></div><div =
style=3D"font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none; font-family: =
Calibri, Helvetica, sans-serif; font-size: 12pt;" =
class=3D"">Thanks!</div><div style=3D"font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none; font-family: Calibri, Helvetica, sans-serif; =
font-size: 12pt;" class=3D"">Hoil Choi</div><div style=3D"font-style: =
normal; font-variant-caps: normal; font-weight: normal; letter-spacing: =
normal; text-align: start; text-indent: 0px; text-transform: none; =
white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none; font-family: Calibri, Helvetica, sans-serif; =
font-size: 12pt;" class=3D"">253-273-5442</div><div style=3D"font-style: =
normal; font-variant-caps: normal; font-weight: normal; letter-spacing: =
normal; text-align: start; text-indent: 0px; text-transform: none; =
white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none; font-family: Calibri, Helvetica, sans-serif; =
font-size: 12pt;" class=3D""><br class=3D""></div><span =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
12px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none; float: none; =
display: inline !important;" =
class=3D"">_______________________________________________</span><br =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
12px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none;" class=3D""><span =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
12px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none; float: none; =
display: inline !important;" class=3D"">sipcore mailing list</span><br =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
12px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none;" class=3D""><a =
href=3D"mailto:sipcore@ietf.org" style=3D"font-family: Helvetica; =
font-size: 12px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; orphans: auto; text-align: =
start; text-indent: 0px; text-transform: none; white-space: normal; =
widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; =
-webkit-text-stroke-width: 0px;" class=3D"">sipcore@ietf.org</a><br =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
12px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none;" class=3D""><a =
href=3D"https://www.ietf.org/mailman/listinfo/sipcore" =
style=3D"font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
orphans: auto; text-align: start; text-indent: 0px; text-transform: =
none; white-space: normal; widows: auto; word-spacing: 0px; =
-webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px;" =
class=3D"">https://www.ietf.org/mailman/listinfo/sipcore</a></div></blockq=
uote></div><br class=3D""></div></body></html>=

--Apple-Mail=_30CFEED2-23DF-4AAF-A125-146F9A346D5B--


From nobody Fri May 28 12:38:41 2021
Return-Path: <ranjitkav12@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 052C53A3331 for <sipcore@ietfa.amsl.com>; Fri, 28 May 2021 12:38:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.847
X-Spam-Level: 
X-Spam-Status: No, score=-1.847 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, 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 YkS6wCp0GATw for <sipcore@ietfa.amsl.com>; Fri, 28 May 2021 12:38:37 -0700 (PDT)
Received: from mail-ej1-x62b.google.com (mail-ej1-x62b.google.com [IPv6:2a00:1450:4864:20::62b]) (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 27E903A3330 for <sipcore@ietf.org>; Fri, 28 May 2021 12:38:37 -0700 (PDT)
Received: by mail-ej1-x62b.google.com with SMTP id z12so7101331ejw.0 for <sipcore@ietf.org>; Fri, 28 May 2021 12:38:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=cbPmnqe5cCbqtTR3vIkqmWcdForh8jbH/LMYtj27JCk=; b=JdWoNLpgBfVle5TzO7g9XADApKY2Z27jOmjrErJslB40foL2dlVFewWu2fCNEilhi4 eJT62npFsoFlGcNmwBo6X94x4CjvzNzf3nm15Hs06gHTHnMNyFTr+2hT4j2+l9Bm6x3p MAfArbvalebNhvc+AkXgbivCuSvw9VUgBJejJSV9XKNRN8bE6rF6r5pwEBEFkCz7n2ua chzGJKusP1P68DI9DE7/SbEpniyZuhTdAiI5eI2eUy8XPAGbrWO+6kTyTimxmL/gGLah 7z8oAkL5I8F0+eNz/bgc1bTZmPLsn34xH1djRd9DuH67Z8lTutCasT0xiNY5yBKv+dER Nyvg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=cbPmnqe5cCbqtTR3vIkqmWcdForh8jbH/LMYtj27JCk=; b=nkG6+GblspjtLsfGah7blrO0eFwDbkSBGN5VreaD1hfh0je89kIG5Ng2iD6HF6lM+K Kq/+Neoy1FeOza3d5yE4AMJxZJX3zjZp+klGcQC6ffEdb4wv6vIVjwKYgmNZWBk6oomM yRr/3CkMlBNPKFGV3EcgrRcXKP7DD8dT22Rs7sLCUtK9tHvsncyBOo4sm/uwqsaUURnB sWU9pQSjOiZePE/bJK3Q7scuFL8qDB03eavBk7R0m7B6gAmFfKly+agVT04I7odUbEgs jmbZMqtD5y9j8Fc3fsUGIxZ+8D8wFiu0V9byQePV9TvZYRXVcindTA3BqkZXsGVtqTq/ eg5w==
X-Gm-Message-State: AOAM530nEi3CxxxGdUlLw70ISZ1io/wki7LcdtiPpnvqjmGFcu08a/kz 5jf2iLMUTPBVYHpa7kTsJWgyGbNPcH7xCtqBE+w=
X-Google-Smtp-Source: ABdhPJyCGB8Wj8JpugYxBLvGTPzt3+p3qvjLQu4gI4wQqRobvfAeXVEJK1M5BmX9w/x0wxm3SNCuWOT4lRmQ4yClBJ8=
X-Received: by 2002:a17:906:55d6:: with SMTP id z22mr10685008ejp.355.1622230714037;  Fri, 28 May 2021 12:38:34 -0700 (PDT)
MIME-Version: 1.0
References: <CO6PR02MB7603DC7C115904E3A41C9A95EE229@CO6PR02MB7603.namprd02.prod.outlook.com>
In-Reply-To: <CO6PR02MB7603DC7C115904E3A41C9A95EE229@CO6PR02MB7603.namprd02.prod.outlook.com>
From: Ranjit Avasarala <ranjitkav12@gmail.com>
Date: Fri, 28 May 2021 14:38:09 -0500
Message-ID: <CAFXT-pvFCev5CJ=chpGfHTQOMQ-J1=sBqwZDXLEgyU2i4dSsOQ@mail.gmail.com>
To: Hoil Choi <hoil.choi@hotmail.com>, Sip-implementors@lists.cs.columbia.edu
Cc: "sipcore@ietf.org" <sipcore@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000007437f205c3690590"
Archived-At: <https://mailarchive.ietf.org/arch/msg/sipcore/nCJyxt8VOwR8YhxHfhM2HwuhhhU>
Subject: Re: [sipcore] RFC 4028 UAS behavior requirement of Require header
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: Fri, 28 May 2021 19:38:39 -0000

--0000000000007437f205c3690590
Content-Type: text/plain; charset="UTF-8"

Hi Holi
the presence of the "Require" header with value "timer" from UAS indicates
to UAC that it (UAC) is performing the refreshing operation. but if the UAS
is the refresher, then if Require header with value "timer" is present in
response from UAS, then UAC should send BYE if it does not receive a
session refresh request from UAS.

Regards
Ranjit



On Fri, May 28, 2021 at 10:02 AM Hoil Choi <hoil.choi@hotmail.com> wrote:

> Hello,
>
> I hope this mail finds appropriate person or team for an answer to my
> question on RFC 4028.
> I am a SIP enthusiast and always learning a lot about it, but by no means
> am I an expert; so please excuse my ignorance.
>
> I came across an interesting statement In Section 9 UAS Behavior (or page
> 16).
>
>
> If the refresher parameter in the Session-Expires header field in the
>    2xx response has a value of 'uac', the UAS MUST place a Require
>    header field into the response with the value 'timer'.
>
>
> Statement seems to convey that UAS must place a Require header with value
> 'timer' when UAC requests itself to be the refresher.
>
> However, this statement should only be true, if UAC did not put
> Session-Expire with value of 'uac'.
>
> If UAC, in INVITE request, put Session-Expire with value of 'uac'
> (itself), UAS should not bother putting Require header field in the
> response.  Or to be more accurate, UAC should include 'timer' in Supported
> header, so that UAS doesn't have to bother putting Require header field.
>
> What is the reason behind the requirement of Require header, from UAS in
> this case?
>
> Thanks!
> Hoil Choi
> 253-273-5442
>
> _______________________________________________
> sipcore mailing list
> sipcore@ietf.org
> https://www.ietf.org/mailman/listinfo/sipcore
>

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

<div dir=3D"ltr">Hi Holi<div>the presence of the &quot;Require&quot; header=
 with value &quot;timer&quot; from UAS indicates to UAC that it (UAC) is pe=
rforming the refreshing operation. but if the UAS is the refresher, then if=
 Require header with value &quot;timer&quot; is present in response from UA=
S, then UAC should send BYE if it does not receive a session refresh reques=
t from UAS.</div><div><br></div><div>Regards</div><div>Ranjit</div><div><br=
></div><div><br></div></div><br><div class=3D"gmail_quote"><div dir=3D"ltr"=
 class=3D"gmail_attr">On Fri, May 28, 2021 at 10:02 AM Hoil Choi &lt;<a hre=
f=3D"mailto:hoil.choi@hotmail.com">hoil.choi@hotmail.com</a>&gt; wrote:<br>=
</div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;b=
order-left:1px solid rgb(204,204,204);padding-left:1ex">




<div dir=3D"ltr">
<div style=3D"font-family:Calibri,Helvetica,sans-serif;font-size:12pt;color=
:rgb(0,0,0)">
Hello,=C2=A0</div>
<div style=3D"font-family:Calibri,Helvetica,sans-serif;font-size:12pt;color=
:rgb(0,0,0)">
<br>
</div>
<div style=3D"font-family:Calibri,Helvetica,sans-serif;font-size:12pt;color=
:rgb(0,0,0)">
I hope this mail finds appropriate person or team for an answer to my quest=
ion on RFC 4028.=C2=A0</div>
<div style=3D"font-family:Calibri,Helvetica,sans-serif;font-size:12pt;color=
:rgb(0,0,0)">
I am a SIP enthusiast and always learning a lot about it, but by no means a=
m I an expert; so please excuse my ignorance. =C2=A0</div>
<div style=3D"font-family:Calibri,Helvetica,sans-serif;font-size:12pt;color=
:rgb(0,0,0)">
<br>
</div>
<div style=3D"font-family:Calibri,Helvetica,sans-serif;font-size:12pt;color=
:rgb(0,0,0)">
I came across an interesting statement In Section 9 UAS Behavior (or page 1=
6).</div>
<div style=3D"font-family:Calibri,Helvetica,sans-serif;font-size:12pt;color=
:rgb(0,0,0)">
<pre style=3D"font-weight:400;font-size:13.3333px;margin-top:0px;margin-bot=
tom:0px;break-before:page"><br></pre>
<pre style=3D"font-weight:400;font-size:13.3333px;margin-top:0px;margin-bot=
tom:0px;break-before:page">If the refresher parameter in the Session-Expire=
s header field in the
=C2=A0 =C2=A02xx response has a value of &#39;uac&#39;, the UAS MUST place =
a Require
=C2=A0 =C2=A0header field into the response with the value &#39;timer&#39;.=
 </pre>
<br>
</div>
<div style=3D"font-family:Calibri,Helvetica,sans-serif;font-size:12pt;color=
:rgb(0,0,0)">
Statement seems to convey that UAS must place a Require header with value &=
#39;timer&#39; when UAC requests itself to be the refresher. =C2=A0</div>
<div style=3D"font-family:Calibri,Helvetica,sans-serif;font-size:12pt;color=
:rgb(0,0,0)">
<br>
</div>
<div style=3D"font-family:Calibri,Helvetica,sans-serif;font-size:12pt;color=
:rgb(0,0,0)">
However, this statement should only be true, if UAC did not put Session-Exp=
ire with value of &#39;uac&#39;. =C2=A0</div>
<div style=3D"font-family:Calibri,Helvetica,sans-serif;font-size:12pt;color=
:rgb(0,0,0)">
<br>
</div>
<div style=3D"font-family:Calibri,Helvetica,sans-serif;font-size:12pt;color=
:rgb(0,0,0)">
If UAC, in INVITE request, put Session-Expire with value of &#39;uac&#39; (=
itself), UAS should not bother putting Require header field in the response=
.=C2=A0 Or to be more accurate, UAC should include &#39;timer&#39; in Suppo=
rted header, so that UAS doesn&#39;t have to bother putting
 Require header field. =C2=A0</div>
<div style=3D"font-family:Calibri,Helvetica,sans-serif;font-size:12pt;color=
:rgb(0,0,0)">
<br>
</div>
<div style=3D"font-family:Calibri,Helvetica,sans-serif;font-size:12pt;color=
:rgb(0,0,0)">
What is the reason behind the requirement of Require header, from UAS in th=
is case?</div>
<div style=3D"font-family:Calibri,Helvetica,sans-serif;font-size:12pt;color=
:rgb(0,0,0)">
<br>
</div>
<div style=3D"font-family:Calibri,Helvetica,sans-serif;font-size:12pt;color=
:rgb(0,0,0)">
Thanks!</div>
<div style=3D"font-family:Calibri,Helvetica,sans-serif;font-size:12pt;color=
:rgb(0,0,0)">
Hoil Choi</div>
<div style=3D"font-family:Calibri,Helvetica,sans-serif;font-size:12pt;color=
:rgb(0,0,0)">
253-273-5442</div>
<div style=3D"font-family:Calibri,Helvetica,sans-serif;font-size:12pt;color=
:rgb(0,0,0)">
<br>
</div>
</div>

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

--0000000000007437f205c3690590--


From nobody Fri May 28 13:41:08 2021
Return-Path: <ranjitkav12@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 592AC3A3514 for <sipcore@ietfa.amsl.com>; Fri, 28 May 2021 13:41:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.746
X-Spam-Level: 
X-Spam-Status: No, score=-1.746 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, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=0.1, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 kp7rcnjjUOEK for <sipcore@ietfa.amsl.com>; Fri, 28 May 2021 13:41:02 -0700 (PDT)
Received: from mail-ed1-x52a.google.com (mail-ed1-x52a.google.com [IPv6:2a00:1450:4864:20::52a]) (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 0B5ED3A3512 for <sipcore@ietf.org>; Fri, 28 May 2021 13:41:01 -0700 (PDT)
Received: by mail-ed1-x52a.google.com with SMTP id j9so6244524edt.6 for <sipcore@ietf.org>; Fri, 28 May 2021 13:41:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=0jK6UGDGEnOkuPuwj6G0lUK/x/pTnTkjdbxjEECVMb0=; b=AVenxVKvuuPhWpf6rrT/do5H7h/vJxksCY3aUeS10CC19zEioQ6W0/DLx6DvVhu6oo LpRhyq0L0gwYgNS9tgXaOReBjBpLoftvQRl6rA4HozmlBgtiR4BrFxFkN6f/5thOaVkE xdXAXWq5w+C24qDWuggeTQDs8IpegAuyKBCZRC1XO2R6q1PLGMHfd3fDN8RQkQroudw9 2lAGx2Q52aSdhFdcZqdB2ncc5OlBgBoOSrggQTShB5UJ+RiutfsKW9bnHXFPvIhqEJKf FzujdgDK/+ItT3HDOYsxVeH9C5EZcKRWI3B9NT3ufNMMVAHvfx3kZaBvZQQc/8Td0eRF iluw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=0jK6UGDGEnOkuPuwj6G0lUK/x/pTnTkjdbxjEECVMb0=; b=jTSUs4N87xhSzPTv+zEzB85Twuf+mlj95nz6WVT7P5iUJuT+fsfdLEQXYxPQ4Eukcv fvHkAksQNMcJOratlWqhRwzUpGR0ZpEnZTiQBiM4P7brp8sw/rldqlAWnlfA+ncyP3+p DD01jYoN48atYHTFymu4fcPHVZIxWeoZPpKFlKNhPUriI6jArBEktQSN8nHwN+ZHiD2l eyqlmnrtpIgedFuNo5VvHltXQE2wtYrh/yMQhSY3l3Cwzf1onFXsidh2IWxbl4ha2KHn exJvVl+BR7yCioqk9Q3OWnDd3oFliT627rS8lJR1eXalrce1ubQ5iegfzGWpMk8ZBHmU VltQ==
X-Gm-Message-State: AOAM533rdtmbudESFWZnSgP0Zyb62UTgLXcEGwHXtdPxIihzDhbwzMpm KvtI+1u05lfKlFldXSzuyUo0OWRu3OF6NpsJAbU=
X-Google-Smtp-Source: ABdhPJzw+T7C1m6eCYdQ8I9dezfvn/Hpiyr2LCF/DSFxEQad8N9PiOTHMP3AZchPom+ITyWQr5PyFJLcE4oiJi6KwQk=
X-Received: by 2002:a05:6402:13d9:: with SMTP id a25mr10625993edx.387.1622234458209;  Fri, 28 May 2021 13:40:58 -0700 (PDT)
MIME-Version: 1.0
References: <CO6PR02MB7603DC7C115904E3A41C9A95EE229@CO6PR02MB7603.namprd02.prod.outlook.com> <CAFXT-pvFCev5CJ=chpGfHTQOMQ-J1=sBqwZDXLEgyU2i4dSsOQ@mail.gmail.com> <CO6PR02MB76038D3A73C42781CC2D3DE2EE229@CO6PR02MB7603.namprd02.prod.outlook.com>
In-Reply-To: <CO6PR02MB76038D3A73C42781CC2D3DE2EE229@CO6PR02MB7603.namprd02.prod.outlook.com>
From: Ranjit Avasarala <ranjitkav12@gmail.com>
Date: Fri, 28 May 2021 15:40:33 -0500
Message-ID: <CAFXT-psukQPK4+x9gH8x9NbXsEyC2oTehW1oVJPk+bAm_4nYrA@mail.gmail.com>
To: Hoil Choi <hoil.choi@hotmail.com>
Cc: "Sip-implementors@lists.cs.columbia.edu" <Sip-implementors@lists.cs.columbia.edu>,  "sipcore@ietf.org" <sipcore@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000009fc17c05c369e467"
Archived-At: <https://mailarchive.ietf.org/arch/msg/sipcore/ppvk867p2q9MaZU-w4L7vEKB1hk>
Subject: Re: [sipcore] RFC 4028 UAS behavior requirement of Require header
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: Fri, 28 May 2021 20:41:06 -0000

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

Hi Holi

The RFC says UAS should add a Require: timer in response when UAC is the
refresher to indicate to UAC that it is the refresher. But I think this is
redundant as UAC anyway knows it is the refresher and does not need a
reminder from UAS.

On Fri, May 28, 2021 at 3:18 PM Hoil Choi <hoil.choi@hotmail.com> wrote:

> Hi Ranjit, thanks for taking a look.
>
> However, I'm more interested in case where UAS is responding to UAC's
> request with refresher as itself (uac).  Consider this case -
>
> UAC ---- INVITE (Session-Expires: 1800;refresher=3Duac, Supported: timer)
> ----> UAS
> UAC <---- 200 OK (Session-Expires: 1800;refresher=3Duac)
> --------------------- UAS
>
> In this case, the statement in question seems to convey that UAS should
> also add "Require: timer" in its 200 response.  Why would this be, when
> it's clear that UAC declared itself as the refresher and that timer is
> supported?
>
> For reference, RFC 4028 Section 9 UAS Behavior (or page 16)
> If the refresher parameter in the Session-Expires header field in the 2xx
> response has a value of 'uac', the UAS MUST place a Require header field
> into the response with the value 'timer'.
>
> Thanks,
> Hoil
>
> ------------------------------
> *From:* Ranjit Avasarala <ranjitkav12@gmail.com>
> *Sent:* Friday, May 28, 2021 12:38 PM
> *To:* Hoil Choi <hoil.choi@hotmail.com>;
> Sip-implementors@lists.cs.columbia.edu <
> Sip-implementors@lists.cs.columbia.edu>
> *Cc:* sipcore@ietf.org <sipcore@ietf.org>
> *Subject:* Re: [sipcore] RFC 4028 UAS behavior requirement of Require
> header
>
> Hi Holi
> the presence of the "Require" header with value "timer" from UAS indicate=
s
> to UAC that it (UAC) is performing the refreshing operation. but if the U=
AS
> is the refresher, then if Require header with value "timer" is present in
> response from UAS, then UAC should send BYE if it does not receive a
> session refresh request from UAS.
>
> Regards
> Ranjit
>
>
>
> On Fri, May 28, 2021 at 10:02 AM Hoil Choi <hoil.choi@hotmail.com> wrote:
>
> Hello,
>
> I hope this mail finds appropriate person or team for an answer to my
> question on RFC 4028.
> I am a SIP enthusiast and always learning a lot about it, but by no means
> am I an expert; so please excuse my ignorance.
>
> I came across an interesting statement In Section 9 UAS Behavior (or page
> 16).
>
>
> If the refresher parameter in the Session-Expires header field in the
>    2xx response has a value of 'uac', the UAS MUST place a Require
>    header field into the response with the value 'timer'.
>
>
> Statement seems to convey that UAS must place a Require header with value
> 'timer' when UAC requests itself to be the refresher.
>
> However, this statement should only be true, if UAC did not put
> Session-Expire with value of 'uac'.
>
> If UAC, in INVITE request, put Session-Expire with value of 'uac'
> (itself), UAS should not bother putting Require header field in the
> response.  Or to be more accurate, UAC should include 'timer' in Supporte=
d
> header, so that UAS doesn't have to bother putting Require header field.
>
> What is the reason behind the requirement of Require header, from UAS in
> this case?
>
> Thanks!
> Hoil Choi
> 253-273-5442
>
> _______________________________________________
> sipcore mailing list
> sipcore@ietf.org
> https://www.ietf.org/mailman/listinfo/sipcore
> <https://na01.safelinks.protection.outlook.com/?url=3Dhttps%3A%2F%2Fwww.i=
etf.org%2Fmailman%2Flistinfo%2Fsipcore&data=3D04%7C01%7C%7C4f68f91aa77847f0=
fb6508d922102eb4%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C6375782751556=
41932%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6I=
k1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=3D3McfrKwjz9RwC%2FBRLtdyopgzmNmUqsAKdAXy=
yRvChuc%3D&reserved=3D0>
>
>

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

<div dir=3D"ltr">Hi Holi<div><br></div><div>The RFC says UAS should add a R=
equire: timer in response when UAC is the refresher to indicate to UAC that=
 it is the refresher. But I think this is redundant as UAC anyway knows it =
is the refresher and does not need a reminder from UAS.</div></div><br><div=
 class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Fri, May 28=
, 2021 at 3:18 PM Hoil Choi &lt;<a href=3D"mailto:hoil.choi@hotmail.com">ho=
il.choi@hotmail.com</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quot=
e" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204)=
;padding-left:1ex">




<div dir=3D"ltr">
<div style=3D"font-family:Calibri,Helvetica,sans-serif;font-size:12pt;color=
:rgb(0,0,0)">
Hi Ranjit, thanks=C2=A0for taking a look. =C2=A0</div>
<div style=3D"font-family:Calibri,Helvetica,sans-serif;font-size:12pt;color=
:rgb(0,0,0)">
<br>
</div>
<div style=3D"font-family:Calibri,Helvetica,sans-serif;font-size:12pt;color=
:rgb(0,0,0)">
However, I&#39;m more interested in case where UAS is responding to UAC&#39=
;s request with refresher as itself (uac).=C2=A0 Consider this case -=C2=A0=
</div>
<div style=3D"font-family:Calibri,Helvetica,sans-serif;font-size:12pt;color=
:rgb(0,0,0)">
<br>
</div>
<div style=3D"font-family:Calibri,Helvetica,sans-serif;font-size:12pt;color=
:rgb(0,0,0)">
UAC ---- INVITE (<span style=3D"font-size:9pt">Session-Expires: 1800;refres=
her=3Duac</span><span style=3D"font-size:9pt">,
</span><span style=3D"font-size:9pt">Supported: timer</span>) ----&gt; UAS<=
/div>
<div style=3D"font-family:Calibri,Helvetica,sans-serif;font-size:12pt;color=
:rgb(0,0,0)">
UAC &lt;---- 200 OK (<span style=3D"background-color:rgb(255,255,255);font-=
size:9pt;display:inline">Session-Expires: 1800;refresher=3Duac</span><span =
style=3D"background-color:rgb(255,255,255);display:inline">)
 --------------------- UAS</span></div>
<div style=3D"font-family:Calibri,Helvetica,sans-serif;font-size:12pt;color=
:rgb(0,0,0)">
<span style=3D"background-color:rgb(255,255,255);display:inline"><br>
</span></div>
<div style=3D"font-family:Calibri,Helvetica,sans-serif;font-size:12pt;color=
:rgb(0,0,0)">
<span style=3D"background-color:rgb(255,255,255);display:inline">In this ca=
se, the statement in question seems to convey that UAS should also add &quo=
t;Require: timer&quot; in its 200 response.=C2=A0 Why would this be, when i=
t&#39;s clear that
 UAC declared itself as the refresher and that timer is supported? =C2=A0</=
span></div>
<div style=3D"font-family:Calibri,Helvetica,sans-serif;font-size:12pt;color=
:rgb(0,0,0)">
<span style=3D"background-color:rgb(255,255,255);display:inline"><br>
</span></div>
<div style=3D"font-family:Calibri,Helvetica,sans-serif;font-size:12pt;color=
:rgb(0,0,0)">
<span style=3D"background-color:rgb(255,255,255);display:inline">For refere=
nce, RFC 4028=C2=A0<span style=3D"background-color:rgb(255,255,255);display=
:inline">Section 9 UAS Behavior (or page
 16)</span></span></div>
<div style=3D"font-family:Calibri,Helvetica,sans-serif;font-size:12pt;color=
:rgb(0,0,0)">
<span style=3D"background-color:rgb(255,255,255);display:inline"><span styl=
e=3D"font-family:monospace;font-size:13.3333px;background-color:rgb(255,255=
,255);display:inline">If
 the refresher parameter in the Session-Expires header field in the 2xx res=
ponse has a value of &#39;uac&#39;, the UAS MUST place a Require header fie=
ld into the response with the value &#39;timer&#39;.
</span><br>
</span></div>
<div style=3D"font-family:Calibri,Helvetica,sans-serif;font-size:12pt;color=
:rgb(0,0,0)">
<br>
</div>
<div style=3D"font-family:Calibri,Helvetica,sans-serif;font-size:12pt;color=
:rgb(0,0,0)">
<span style=3D"background-color:rgb(255,255,255);display:inline">Thanks,</s=
pan></div>
<div style=3D"font-family:Calibri,Helvetica,sans-serif;font-size:12pt;color=
:rgb(0,0,0)">
<span style=3D"background-color:rgb(255,255,255);display:inline">Hoil</span=
></div>
<div>
<div id=3D"gmail-m_-8007310680971281901appendonsend"></div>
<div style=3D"font-family:Calibri,Helvetica,sans-serif;font-size:12pt;color=
:rgb(0,0,0)">
<br>
</div>
<hr style=3D"display:inline-block;width:98%">
<div id=3D"gmail-m_-8007310680971281901divRplyFwdMsg" dir=3D"ltr"><font fac=
e=3D"Calibri, sans-serif" color=3D"#000000" style=3D"font-size:11pt"><b>Fro=
m:</b> Ranjit Avasarala &lt;<a href=3D"mailto:ranjitkav12@gmail.com" target=
=3D"_blank">ranjitkav12@gmail.com</a>&gt;<br>
<b>Sent:</b> Friday, May 28, 2021 12:38 PM<br>
<b>To:</b> Hoil Choi &lt;<a href=3D"mailto:hoil.choi@hotmail.com" target=3D=
"_blank">hoil.choi@hotmail.com</a>&gt;; <a href=3D"mailto:Sip-implementors@=
lists.cs.columbia.edu" target=3D"_blank">Sip-implementors@lists.cs.columbia=
.edu</a> &lt;<a href=3D"mailto:Sip-implementors@lists.cs.columbia.edu" targ=
et=3D"_blank">Sip-implementors@lists.cs.columbia.edu</a>&gt;<br>
<b>Cc:</b> <a href=3D"mailto:sipcore@ietf.org" target=3D"_blank">sipcore@ie=
tf.org</a> &lt;<a href=3D"mailto:sipcore@ietf.org" target=3D"_blank">sipcor=
e@ietf.org</a>&gt;<br>
<b>Subject:</b> Re: [sipcore] RFC 4028 UAS behavior requirement of Require =
header</font>
<div>=C2=A0</div>
</div>
<div>
<div dir=3D"ltr">Hi Holi
<div>the presence of the &quot;Require&quot; header with value &quot;timer&=
quot; from UAS indicates to UAC that it (UAC) is performing the refreshing =
operation. but if the UAS is the refresher, then if Require header with val=
ue &quot;timer&quot; is present in response from UAS, then UAC
 should send BYE if it does not receive a session refresh request from UAS.=
</div>
<div><br>
</div>
<div>Regards</div>
<div>Ranjit</div>
<div><br>
</div>
<div><br>
</div>
</div>
<br>
<div>
<div dir=3D"ltr">On Fri, May 28, 2021 at 10:02 AM Hoil Choi &lt;<a href=3D"=
mailto:hoil.choi@hotmail.com" target=3D"_blank">hoil.choi@hotmail.com</a>&g=
t; wrote:<br>
</div>
<blockquote style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204=
,204,204);padding-left:1ex">
<div dir=3D"ltr">
<div style=3D"font-family:Calibri,Helvetica,sans-serif;font-size:12pt;color=
:rgb(0,0,0)">
Hello,=C2=A0</div>
<div style=3D"font-family:Calibri,Helvetica,sans-serif;font-size:12pt;color=
:rgb(0,0,0)">
<br>
</div>
<div style=3D"font-family:Calibri,Helvetica,sans-serif;font-size:12pt;color=
:rgb(0,0,0)">
I hope this mail finds appropriate person or team for an answer to my quest=
ion on RFC 4028.=C2=A0</div>
<div style=3D"font-family:Calibri,Helvetica,sans-serif;font-size:12pt;color=
:rgb(0,0,0)">
I am a SIP enthusiast and always learning a lot about it, but by no means a=
m I an expert; so please excuse my ignorance. =C2=A0</div>
<div style=3D"font-family:Calibri,Helvetica,sans-serif;font-size:12pt;color=
:rgb(0,0,0)">
<br>
</div>
<div style=3D"font-family:Calibri,Helvetica,sans-serif;font-size:12pt;color=
:rgb(0,0,0)">
I came across an interesting statement In Section 9 UAS Behavior (or page 1=
6).</div>
<div style=3D"font-family:Calibri,Helvetica,sans-serif;font-size:12pt;color=
:rgb(0,0,0)">
<pre style=3D"font-weight:400;font-size:13.3333px;margin-top:0px;margin-bot=
tom:0px;break-before:page"><br></pre>
<pre style=3D"font-weight:400;font-size:13.3333px;margin-top:0px;margin-bot=
tom:0px;break-before:page">If the refresher parameter in the Session-Expire=
s header field in the
=C2=A0 =C2=A02xx response has a value of &#39;uac&#39;, the UAS MUST place =
a Require
=C2=A0 =C2=A0header field into the response with the value &#39;timer&#39;.=
 </pre>
<br>
</div>
<div style=3D"font-family:Calibri,Helvetica,sans-serif;font-size:12pt;color=
:rgb(0,0,0)">
Statement seems to convey that UAS must place a Require header with value &=
#39;timer&#39; when UAC requests itself to be the refresher. =C2=A0</div>
<div style=3D"font-family:Calibri,Helvetica,sans-serif;font-size:12pt;color=
:rgb(0,0,0)">
<br>
</div>
<div style=3D"font-family:Calibri,Helvetica,sans-serif;font-size:12pt;color=
:rgb(0,0,0)">
However, this statement should only be true, if UAC did not put Session-Exp=
ire with value of &#39;uac&#39;. =C2=A0</div>
<div style=3D"font-family:Calibri,Helvetica,sans-serif;font-size:12pt;color=
:rgb(0,0,0)">
<br>
</div>
<div style=3D"font-family:Calibri,Helvetica,sans-serif;font-size:12pt;color=
:rgb(0,0,0)">
If UAC, in INVITE request, put Session-Expire with value of &#39;uac&#39; (=
itself), UAS should not bother putting Require header field in the response=
.=C2=A0 Or to be more accurate, UAC should include &#39;timer&#39; in Suppo=
rted header, so that UAS doesn&#39;t have to bother putting
 Require header field. =C2=A0</div>
<div style=3D"font-family:Calibri,Helvetica,sans-serif;font-size:12pt;color=
:rgb(0,0,0)">
<br>
</div>
<div style=3D"font-family:Calibri,Helvetica,sans-serif;font-size:12pt;color=
:rgb(0,0,0)">
What is the reason behind the requirement of Require header, from UAS in th=
is case?</div>
<div style=3D"font-family:Calibri,Helvetica,sans-serif;font-size:12pt;color=
:rgb(0,0,0)">
<br>
</div>
<div style=3D"font-family:Calibri,Helvetica,sans-serif;font-size:12pt;color=
:rgb(0,0,0)">
Thanks!</div>
<div style=3D"font-family:Calibri,Helvetica,sans-serif;font-size:12pt;color=
:rgb(0,0,0)">
Hoil Choi</div>
<div style=3D"font-family:Calibri,Helvetica,sans-serif;font-size:12pt;color=
:rgb(0,0,0)">
253-273-5442</div>
<div style=3D"font-family:Calibri,Helvetica,sans-serif;font-size:12pt;color=
:rgb(0,0,0)">
<br>
</div>
</div>
_______________________________________________<br>
sipcore mailing list<br>
<a href=3D"mailto:sipcore@ietf.org" target=3D"_blank">sipcore@ietf.org</a><=
br>
<a href=3D"https://na01.safelinks.protection.outlook.com/?url=3Dhttps%3A%2F=
%2Fwww.ietf.org%2Fmailman%2Flistinfo%2Fsipcore&amp;data=3D04%7C01%7C%7C4f68=
f91aa77847f0fb6508d922102eb4%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C6=
37578275155641932%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luM=
zIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&amp;sdata=3D3McfrKwjz9RwC%2FBRLtdy=
opgzmNmUqsAKdAXyyRvChuc%3D&amp;reserved=3D0" rel=3D"noreferrer" target=3D"_=
blank">https://www.ietf.org/mailman/listinfo/sipcore</a><br>
</blockquote>
</div>
</div>
</div>
</div>

</blockquote></div>

--0000000000009fc17c05c369e467--


From nobody Mon May 31 05:23:10 2021
Return-Path: <R.Jesske@telekom.de>
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 A5B063A15E7 for <sipcore@ietfa.amsl.com>; Mon, 31 May 2021 05:22:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.093
X-Spam-Level: 
X-Spam-Status: No, score=-5.093 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.698, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=telekom.de
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 eRobd99c6Q74 for <sipcore@ietfa.amsl.com>; Mon, 31 May 2021 05:22:54 -0700 (PDT)
Received: from mailout41.telekom.de (mailout41.telekom.de [194.25.225.151]) (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 4E4103A15C4 for <sipcore@ietf.org>; Mon, 31 May 2021 05:22:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telekom.de; i=@telekom.de; q=dns/txt; s=dtag1; t=1622463774; x=1653999774; h=from:to:cc:subject:date:message-id: content-transfer-encoding:mime-version; bh=i772t7y1DNR+go8CsI5jz0QuCyQBmiBss7QCcTKWRh0=; b=dOrp5Z4B6ek11VzbSCjbFoqf4gikwj1Fs50gvZODZ2g5FJ577yYPqS9/ IjlxpcSbNhqpqyNtsPKp/5xxeNxJd+UaYgcc4yEHvttJ/o8ohvNjcWgGa bwGHL56HQs9iSN7oaWT/aDUeUT1NCDCLdRtimK1i8SIGtY1E8WyYEN2uq RQ+pYzuKvbVGdi1qvnWP9rDYjtlDgtc+Xrf4p94ANn74RCxWie5TeFt1c mGc3rH29Z9TQgCiM9k0A42GrnZ4pnsZI/3UtntJ9q1r+7Olmqgwc/ij/Y nQtbYRo3TRJwAJ4IdhdZIS4ojrg0Q91bAiHkq7kgVJ4xt30ZDRJ1+opWe g==;
IronPort-SDR: BfbKv2IqxMFXj9qWBzjfupE4sNdN/8Q8RRiDE961afDgwSWPQgTlyirh9fbuXWL1gjgWUPmuKa 8pdFgadvJ8gw==
IronPort-HdrOrdr: =?us-ascii?q?A9a23=3AC8Wf6qnswXLGZsA0Z2oWrkol49XpDfPxim?= =?us-ascii?q?dD5ihNYBxZY6Wkfp+V7ZYmPE7P+VUssS8b+exoYJPwPk819fZOkPAs1MSZLX?= =?us-ascii?q?fbUQyTXcBfBOrZsnPd8kLFh5NgPMtbAs9D4dDLZmSS7vyKoDVQcexQvOVvmZ?= =?us-ascii?q?rA7YuwoRYdKHAPV0gJ1XYiNu/xKDwPeOAyP+tCKHPq3Ls9m9PPQwVwUi28PB?= =?us-ascii?q?M4tgr4yuHjpdbDW1orFhQn4A6BgXeD87jhCSWV2R8YTndm3aoi2XKtqX272o?= =?us-ascii?q?yT99WAjjPM3W7a6Jpb3PH7zMFYOcCKgs8Jbh3xlweTYph7UbHqhkF2nAjv0i?= =?us-ascii?q?durDD/mWZmAy1B0QKWQohzm2q15+DU6kdr15Yl8y7BvZKsm72jeNtwMbsxuW?= =?us-ascii?q?sQSGqo16NnhqAg7EsD5RPri7NHSRzHhyjz/N7OSlVjkVe1u2MrlaoJg2VYSp?= =?us-ascii?q?Z2Us4dkWUzxjIfLH47JlOx1GnnKpgZMCjW3ocbTbpbVQGQgoBL+q3iYp0eJG?= =?us-ascii?q?bzfqEygL3d79ENpgEN86Ix/r1pop4vzuNOd6V5?=
Received: from qdec94.de.t-internal.com ([10.171.255.41]) by MAILOUT41.dmznet.de.t-internal.com with ESMTP/TLS/ECDHE-RSA-AES128-GCM-SHA256; 31 May 2021 14:22:32 +0200
IronPort-SDR: 3mvjcoJlAdcKxV3QsiMyxP+E1RFfW7IKGv8mfN1CLgpCDx2Gz3jLHfCrwiil/On8wgqTN8Se86 hoXrGkuG51fZiU1PjaKB2ROmF1Q83ekrM=
X-IronPort-AV: E=Sophos;i="5.83,237,1616454000"; d="scan'208";a="340519477"
X-MGA-submission: =?us-ascii?q?MDH8vsOi42Z5H0AiYkNmXz0NZYZ1w3G4a5GxKj?= =?us-ascii?q?kQV1S04JQhVfWyGVKlewmU01Qn4KYGZUKvN1SnF79JPtDBmZOS4ulMuF?= =?us-ascii?q?9tbMlCqDGlEAUEdGl3TPysn8sJ759WapHhvvwOzLFdJYbEOeEL93OWcH?= =?us-ascii?q?lZ1i2TN4cSok2LjXVpNplXBg=3D=3D?=
Received: from he105715.emea1.cds.t-internal.com ([10.169.118.51]) by QDEC97.de.t-internal.com with ESMTP/TLS/ECDHE-RSA-AES128-SHA256; 31 May 2021 14:22:32 +0200
Received: from HE105716.EMEA1.cds.t-internal.com (10.169.118.52) by HE105715.emea1.cds.t-internal.com (10.169.118.51) with Microsoft SMTP Server (TLS) id 15.0.1497.18; Mon, 31 May 2021 14:22:31 +0200
Received: from HE104164.emea1.cds.t-internal.com (10.171.40.35) by HE105716.EMEA1.cds.t-internal.com (10.169.118.52) with Microsoft SMTP Server (TLS) id 15.0.1497.18 via Frontend Transport; Mon, 31 May 2021 14:22:31 +0200
Received: from DEU01-FR2-obe.outbound.protection.outlook.com (104.47.11.171) by O365mail06.telekom.de (172.30.0.233) with Microsoft SMTP Server (TLS) id 15.0.1497.18; Mon, 31 May 2021 14:22:28 +0200
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=SND+BhOIYu7R5CTL2owSlVek1Otp6qnn0PMA4op6IWvUTOvjqmGpc6/1KPy+xOmwbVUuxqXAB7k1nextonQE3lj7Ac7ynT9Ubtlo/B/lLPmSo7D2zSy7VofpI4Wy/lwOCiSuYtE/7op1XmJiTV1gdoXKmjWtPh0PvMd2YVIrEdDLAj5tn9XVVQdqBCBmd2lVSTk1bpnKvMl8WgEHK84YbIjZSwQvvzl5paIrwq4E+o7mc2YUQHbJr8tkISWnrH+Ho6SA1zeERN7rPEwLUXnQ/AYEusEqIBPWwmWN8H8l/Xl/PM2hVz/MovkezJTivEO8CF3qGDt3K15H1YLMkjwfrw==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;  s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=i772t7y1DNR+go8CsI5jz0QuCyQBmiBss7QCcTKWRh0=; b=XcGhWFYCUZd8h3CpAb11hntEH3pK09zSpINQf47K3U+DiX0F8FL/ZehYlGxud0RPKIeo3Nt6BnRNWpRJqgsNKJbe5BlU8ns01TzDxXqhzxn6j57NE7gPOwkyW2Xe3RutR3N2xxPB52PGz2g6dfUE9kx7eyMw/kxPkKTtsiSiRCcFhJ/cKUIeS2aBdV0bdNxTEQ9LCVMopQjHxbGjV7+JVFxLDMrnKmXHgSmOIf81jIF85ur//bSYNF9JgS1DLIK+k5Rvsisgwf0yNANgTlCokXESsJwXGux6vQn34bGsL0ErozDYj5zCYLPzBN5k9nbAVaiYGj2WhHy2pwF2wdjN4w==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=telekom.de; dmarc=pass action=none header.from=telekom.de; dkim=pass header.d=telekom.de; arc=none
Received: from FR2P281MB0028.DEUP281.PROD.OUTLOOK.COM (2603:10a6:d10:b::7) by FR2P281MB0108.DEUP281.PROD.OUTLOOK.COM (2603:10a6:d10:c::14) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.4195.11; Mon, 31 May 2021 12:22:30 +0000
Received: from FR2P281MB0028.DEUP281.PROD.OUTLOOK.COM ([fe80::6954:efc8:1df0:df99]) by FR2P281MB0028.DEUP281.PROD.OUTLOOK.COM ([fe80::6954:efc8:1df0:df99%8]) with mapi id 15.20.4195.017; Mon, 31 May 2021 12:22:30 +0000
From: <R.Jesske@telekom.de>
To: <sipcore@ietf.org>
CC: <lionel.morand@orange.com>
Thread-Topic: Activity proposal on:  New Version Notification for draft-jesske-update-p-visited-network-03.txt
Thread-Index: AddWF2xU0/aFuwqcQ02H3kk2jGTxbA==
Date: Mon, 31 May 2021 12:22:30 +0000
Message-ID: <FR2P281MB0028D7978CDBF03D63BD8D5EF93F9@FR2P281MB0028.DEUP281.PROD.OUTLOOK.COM>
Accept-Language: de-DE, en-US
Content-Language: de-DE
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=none action=none header.from=telekom.de;
x-originating-ip: [87.158.195.232]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: e9b30d72-7c3b-47a3-901a-08d9242ec30d
x-ms-traffictypediagnostic: FR2P281MB0108:
x-microsoft-antispam-prvs: <FR2P281MB010818C4A371C3F860A49836F93F9@FR2P281MB0108.DEUP281.PROD.OUTLOOK.COM>
x-ms-oob-tlc-oobclassifiers: OLM:9508;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: rzgEsGnd8xYbpkB0ZORjjSxBMZei7N1dMobbXHAQP6/2Bm6fBqIJXZw8IOrWfAZFmz6VplgMafhQfMBqswyTIWlzGkGLAfZorJgNLphQTfH7eYMaJqSjWx+/NDg7N9ibRB2b9KsZkYSz6qrVIunmqkSpHd6+Qla0OWtTfiPi0eNjCazs7GQLfn6JfCbCzmQ+GnHTbGBZ9Ft45HWo8iqTWz+dflRixoMRAOoQwos12TQgFtfmyQvqfHx8GTLpnSF2666bRLHndcAsQN5JvUyWdK+fdibiLzodWboCxQgA8XQ7aaJ23e4n1D/dZOo5jh0mqrFPI2BwJlol44Ad1FTwAq3r1o21ZccXAlPcEOaM22eh6hX2UiyTWL7SZTB574pU2NK6A3U2HH+8L5tYwwI3Volis5kajSpjdvEHIQKK7d7l5EKBf311V2hVp3wsFRc3a3SuhOJJvUavhDBuUkHSMotSfFP/g+9WSRIhZ2vDGYrbF4hnW797JlC35ZeUgZ6InJruTpfZmYo4ufCWiKnxJBmffDbJqExkDA1TPSuXK2S4vxmyQhotbxF+m/e1bB8jpgvCh1KA8m8EGwC6zrW+2d+AjFAs8NgNWoT0v+XaLRkeb2UnC+k4G5p1LKZtNagRpn2ko5gsv0O562UdPixjZi7ZESM7/HVJWxkbA7DwIbmgV6Zf448nkbewPi31DcbS+K989CIgXNgTYS54pCaqpw==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:;  IPV:NLI; SFV:NSPM; H:FR2P281MB0028.DEUP281.PROD.OUTLOOK.COM; PTR:; CAT:NONE;  SFS:(366004)(9686003)(6506007)(8676002)(186003)(4326008)(8936002)(7696005)(6916009)(122000001)(5660300002)(83380400001)(66946007)(86362001)(15650500001)(66574015)(2906002)(26005)(66476007)(71200400001)(55016002)(966005)(52536014)(76116006)(66446008)(64756008)(66556008)(498600001)(33656002)(38100700002); DIR:OUT; SFP:1101; 
x-ms-exchange-antispam-messagedata: NAXcO8NW8URMTF9UjaZBd8U2zNOhL52uaJbPerdsMgCY1pJeMlr317wtx2RmpTWZsLO6a02w6wPnCoEkYDU+pC6NvsRYrF9U6mUTTh9PhxwDw6hj7B/FQSq7ji9Or6HfVVRtxB8jc0ujjGfOcDfBmeiXxP28l46iHbGPbuVJ9x/IddOheHGL9aK0UnH6JpxTO4CodksYlN9q5KStNN7dckXKOtJ7i+yFNT3U+aMwf/lVQy8xQw6syPHdRBlFnYZC7J+POPavPiUA9RveA/iEE35oTMIBid7SGCfdVuAWwLvh7lf332reCsOHdIUWHQHzvinjuO5qbJCdMNv+WrRGPAAg+f5U9UQaa6qgTRR2/DuBE8GXJKa6yjC3veX9w4QMKtx7gRbop0KkJsSaYjhkeKZUSae2sC85um3KeEdJTOpPnDV1h/c1ZpPsObp+qodwdUOemPWWKgRwxjZupUUIit1eeGglLKbuY2cMg9HKznGeSLPVFSCcIR6HdYDLQ/Wh2XzQRKkxZX/4MEhhnslZAz7fmtriEBH/dBLa2Z96eNi1YBC4bJJgbe8rypsxXJX2VpgSG0j6bs3OqjqvwKr76SwU3eOBsedyCBhhwlTOQSKnMj+ar4Nmq9W+DtXO/jLLIFbqWP6oi9MQrK4bY5QH0VzSasvJZrLm8hkI7LiF/QRB3VcMmc159/J0wwzcfzJolu9mKFQldg7Ccy7XlFnR5Rh6QvyxTSq/IB4WnzuQ7ayJn3N5CS3uYTC+w4c7B5Rw
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: FR2P281MB0028.DEUP281.PROD.OUTLOOK.COM
X-MS-Exchange-CrossTenant-Network-Message-Id: e9b30d72-7c3b-47a3-901a-08d9242ec30d
X-MS-Exchange-CrossTenant-originalarrivaltime: 31 May 2021 12:22:30.8520 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bde4dffc-4b60-4cf6-8b04-a5eeb25f5c4f
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: ufz8TLJcn7jfWAkMxEutnBLynlZsKXzRCVEbfnV0GWOh5NtnvnaVm/cXsGIUSLgtFXX/mDhvCZO73+5jVHiqJw==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: FR2P281MB0108
X-OriginatorOrg: telekom.de
Archived-At: <https://mailarchive.ietf.org/arch/msg/sipcore/cE0-EEHUpW4Qiirar5mgkB9T3ns>
Subject: [sipcore] Activity proposal on: New Version Notification for draft-jesske-update-p-visited-network-03.txt
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: Mon, 31 May 2021 12:23:09 -0000

DQpEZWFyIGFsbCwNClRoZXJlIGlzIHN0aWxsIGFuIGlzc3VlIHRoYXQgaXMgb3BlbiB3aXRoIHJl
Z2FyZCB0byBkZXBlbmRlbmNpZXMgd2UgaGF2ZSB3aXRoIDNHUFAuDQpSZWZlcnJpbmcgdG86DQoN
Cmh0dHBzOi8vbWFpbGFyY2hpdmUuaWV0Zi5vcmcvYXJjaC9tc2cvc2lwY29yZS84NmdEYlBWY0lU
YTRISDRNZzNxTGgwTGJDTVEvDQoNCkl0IHdvdWxkIGJlIG5pY2UgaWYgd2UgY2FuIHRha2UgdGhl
IGFjdGl2aXR5IG5vdyBhbmQgZmluYWxpemUgdGhlIGJlbG93IG1lbnRpb25lZCBkcmFmdC4NCg0K
U2VlbiBmcm9tIDNHUFAgcGVyc3BlY3RpdmUgaXQgd291bGQgYmUgaW1wb3J0YW50IHRvIGZpbmFs
aXplIHRoaXMgYWN0aXZpdHkgdGhhdCB3ZSBjYW4gcHJvY2VlZCB3aXRoIHRoZSBmaW5hbCBzb2x1
dGlvbi4NCg0KVGhhbmsgeW91IGFuZCBCZXN0IFJlZ2FyZHMNCg0KUm9sYW5kDQoNCi0tLS0tVXJz
cHLDvG5nbGljaGUgTmFjaHJpY2h0LS0tLS0NClZvbjogaW50ZXJuZXQtZHJhZnRzQGlldGYub3Jn
IDxpbnRlcm5ldC1kcmFmdHNAaWV0Zi5vcmc+IA0KR2VzZW5kZXQ6IE1vbnRhZywgMzEuIE1haSAy
MDIxIDE0OjE2DQpBbjogSmVzc2tlLCBSb2xhbmQgPFIuSmVzc2tlQHRlbGVrb20uZGU+DQpCZXRy
ZWZmOiBOZXcgVmVyc2lvbiBOb3RpZmljYXRpb24gZm9yIGRyYWZ0LWplc3NrZS11cGRhdGUtcC12
aXNpdGVkLW5ldHdvcmstMDMudHh0DQoNCg0KQSBuZXcgdmVyc2lvbiBvZiBJLUQsIGRyYWZ0LWpl
c3NrZS11cGRhdGUtcC12aXNpdGVkLW5ldHdvcmstMDMudHh0DQpoYXMgYmVlbiBzdWNjZXNzZnVs
bHkgc3VibWl0dGVkIGJ5IFJvbGFuZCBKZXNza2UgYW5kIHBvc3RlZCB0byB0aGUgSUVURiByZXBv
c2l0b3J5Lg0KDQpOYW1lOgkJZHJhZnQtamVzc2tlLXVwZGF0ZS1wLXZpc2l0ZWQtbmV0d29yaw0K
UmV2aXNpb246CTAzDQpUaXRsZToJCVVwZGF0ZSB0byBQcml2YXRlIEhlYWRlciBGaWVsZCBQLVZp
c2l0ZWQtTmV0d29yay1JRCBpbiBTZXNzaW9uIEluaXRpYXRpb24gUHJvdG9jb2wgKFNJUCkgUmVx
dWVzdHMgYW5kIFJlc3BvbnNlcw0KRG9jdW1lbnQgZGF0ZToJMjAyMS0wNS0zMQ0KR3JvdXA6CQlJ
bmRpdmlkdWFsIFN1Ym1pc3Npb24NClBhZ2VzOgkJNA0KVVJMOiAgICAgICAgICAgIGh0dHBzOi8v
d3d3LmlldGYub3JnL2FyY2hpdmUvaWQvZHJhZnQtamVzc2tlLXVwZGF0ZS1wLXZpc2l0ZWQtbmV0
d29yay0wMy50eHQNClN0YXR1czogICAgICAgICBodHRwczovL2RhdGF0cmFja2VyLmlldGYub3Jn
L2RvYy9kcmFmdC1qZXNza2UtdXBkYXRlLXAtdmlzaXRlZC1uZXR3b3JrLw0KSHRtbGl6ZWQ6ICAg
ICAgIGh0dHBzOi8vZGF0YXRyYWNrZXIuaWV0Zi5vcmcvZG9jL2h0bWwvZHJhZnQtamVzc2tlLXVw
ZGF0ZS1wLXZpc2l0ZWQtbmV0d29yaw0KRGlmZjogICAgICAgICAgIGh0dHBzOi8vd3d3LmlldGYu
b3JnL3JmY2RpZmY/dXJsMj1kcmFmdC1qZXNza2UtdXBkYXRlLXAtdmlzaXRlZC1uZXR3b3JrLTAz
DQoNCkFic3RyYWN0Og0KICAgVGhlIFRoaXJkIEdlbmVyYXRpb24gUGFydG5lcnNoaXAgUHJvamVj
dCAoM0dQUCkgaGFzIGlkZW50aWZpZWQgY2FzZXMNCiAgIHdoZXJlIHRoZSBwcml2YXRlIGhlYWRl
ciBmaWVsZCBQLVZpc2l0ZWQtTmV0d29yay1JRCBTSVAgcHJpdmF0ZQ0KICAgaGVhZGVyIGV4dGVu
c2lvbnMsIHdoaWNoIGlzIGRlZmluZWQgaW4gUkZDIDczMTUgYW5kIHVwZGF0ZWQgYnkgUkZDDQog
ICA3OTc2LCBuZWVkcyB0byBiZSBpbmNsdWRlZCBpbiBTSVAgcmVxdWVzdHMgYW5kIHJlc3BvbnNl
cy4gIFRoaXMNCiAgIGRvY3VtZW50IHVwZGF0ZXMgUkZDIDc5NzYsIGluIG9yZGVyIHRvIGFsbG93
IGluY2x1c2lvbiBvZiB0aGUgUC0NCiAgIFZpc2l0ZWQtTmV0d29yay1JRCBoZWFkZXIgZmllbGQg
aW4gcmVzcG9uc2VzLg0KDQogICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgDQoNCg0KVGhlIElFVEYg
U2VjcmV0YXJpYXQNCg0KDQo=


From nobody Mon May 31 06:51:25 2021
Return-Path: <hoil.choi@hotmail.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 C26383A3466 for <sipcore@ietfa.amsl.com>; Fri, 28 May 2021 13:18:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level: 
X-Spam-Status: No, score=-1.998 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_FROM=0.001, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=0.1, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=hotmail.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 waAIFb9S1pTO for <sipcore@ietfa.amsl.com>; Fri, 28 May 2021 13:18:39 -0700 (PDT)
Received: from NAM11-BN8-obe.outbound.protection.outlook.com (mail-bn8nam11olkn2083.outbound.protection.outlook.com [40.92.20.83]) (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 08BED3A3464 for <sipcore@ietf.org>; Fri, 28 May 2021 13:18:38 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=FUGLpSW2F9jABYILD5om+guwtbAovdoWIYf4EWaMQRCbledogINqGtsSizKtKoVhB6UmDMLlXtn7Iy7vFu7tLFebi1LEAIjjSEnfX2vTrTxoAW2eK6V3lmydab3UkDLEGEkNsqAr5SDvDzIq39Pmnkyf58s4ZyWnMP82bTxVFTXT8uclzkB7jTm1TGLlS05D120ip+KMLXmXAdoDxaM95Cpq6ronjuv1Ltrz+Mc+SJGPGbvOyQ8JY3htjFhNaWNYLtpciEmEsx+vU0nH0/HJ9P5pRqFhMGEpV7fp0a+7uR/8T9aEoMIKdAPAAjl4xEQhVZcxp25+SbGslLVISXVYsA==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;  s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=NDrsRGMxVMsTQCwuZFoQRvfe0CFfZ89lRkcyP1hHvgc=; b=BRaqCqLDz+nCtbzycg5UFp1WV7FCGdtn9EMULDmab9TfMMz6/Pnd4mTlf1orIEOT+VlBDBbpZyFdMWAUay95kWrCZYDoUuJw1bAPANe90cw3x4pgaBaQdv6VlVhD8YmVD64rAGkTu3NAEvECAm9B+jYrEbj/235j3V051lwFhI33UKf6P3xRGLW150uLeu98Cy+DDIOD6nFxtxtosrC9/0suzC0OsXlbDzvafL2NhryNqH2vjC1GyxLiB06Aayw5e5uEoWnaovhEEUSOYmRGF3rv71AXeHIBglIuzh/FNWZ0X5PQoonOfiMMsUU3JU3UNhiXgNI07O+7T3mZgvyNjg==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=none; dmarc=none; dkim=none; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hotmail.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=NDrsRGMxVMsTQCwuZFoQRvfe0CFfZ89lRkcyP1hHvgc=; b=QrSNOEO/9ZtfO3ZB4PcNIIZN+32dbqNjAFR//+CjFToprFQGymmXdreEvx5yYdU9a88GLH9dlwi46vjo3lYMnHuYtpsyHB+Vm0JUuEi01tObIBhFmN+68nVz4S2UKVB0txnkFNxBZ+cog111W8ELJQ5aMRW5FuP5P1VD88Ul2iW+nyc3ywQ63wp8PYJ7uxGr4nL0RLbOcVCFbhWJ0obj6oyTqoqX6yjfuscxXWI9QdSvVgfYZ5t8809sQaUvVu9D1tKLp8ZSGKeFbn+W5pxEi00wSHKOi1uo2+wwIo4quikWOZJGMvQ37CGQTEuofc0BQj4QxYvCjM4sYIFi4h5psg==
Received: from DM6NAM11FT026.eop-nam11.prod.protection.outlook.com (2a01:111:e400:fc4d::40) by DM6NAM11HT175.eop-nam11.prod.protection.outlook.com (2a01:111:e400:fc4d::402) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.4129.25; Fri, 28 May 2021 20:18:36 +0000
Received: from CO6PR02MB7603.namprd02.prod.outlook.com (2a01:111:e400:fc4d::40) by DM6NAM11FT026.mail.protection.outlook.com (2a01:111:e400:fc4d::161) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.4150.30 via Frontend Transport; Fri, 28 May 2021 20:18:36 +0000
Received: from CO6PR02MB7603.namprd02.prod.outlook.com ([fe80::11c6:9a98:84a:7f22]) by CO6PR02MB7603.namprd02.prod.outlook.com ([fe80::11c6:9a98:84a:7f22%7]) with mapi id 15.20.4173.027; Fri, 28 May 2021 20:18:36 +0000
From: Hoil Choi <hoil.choi@hotmail.com>
To: Ranjit Avasarala <ranjitkav12@gmail.com>, "Sip-implementors@lists.cs.columbia.edu" <Sip-implementors@lists.cs.columbia.edu>
CC: "sipcore@ietf.org" <sipcore@ietf.org>
Thread-Topic: [sipcore] RFC 4028 UAS behavior requirement of Require header
Thread-Index: AQHXU42WCj5aHc4bTkuBkpJKe+ECaKr5St6AgAAHxtQ=
Date: Fri, 28 May 2021 20:18:36 +0000
Message-ID: <CO6PR02MB76038D3A73C42781CC2D3DE2EE229@CO6PR02MB7603.namprd02.prod.outlook.com>
References: <CO6PR02MB7603DC7C115904E3A41C9A95EE229@CO6PR02MB7603.namprd02.prod.outlook.com>, <CAFXT-pvFCev5CJ=chpGfHTQOMQ-J1=sBqwZDXLEgyU2i4dSsOQ@mail.gmail.com>
In-Reply-To: <CAFXT-pvFCev5CJ=chpGfHTQOMQ-J1=sBqwZDXLEgyU2i4dSsOQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-incomingtopheadermarker: OriginalChecksum:6975C097A3EBED95C4FF98F74F8EA3728B6CAB1A6D3ABAA94FA3BDA4BFF0AF98; UpperCasedChecksum:A9407BEFA058CCC341953244D35AB80D98D786B81456B3F897D26B9407CC07A1; SizeAsReceived:7158; Count:45
x-ms-exchange-messagesentrepresentingtype: 1
x-tmn: [QaomksQbqiKZc2aIKlgA2Cu6HVeVhjVo]
x-ms-publictraffictype: Email
x-incomingheadercount: 45
x-eopattributedmessage: 0
x-ms-office365-filtering-correlation-id: 61231480-6ecd-49f6-18b9-08d92215c658
x-ms-traffictypediagnostic: DM6NAM11HT175:
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: tmOVPd0ApV6yzIzosWlz8R/7FrAW+D1AWGBGrNa6JIlZG0WF4jGwh1/9z74c7CzVqhUDqV1mCMlYRYSnCnd87p1yT5tvNYGY3LwhOkiYmpZlVgYgf3PklfxVQpZtKdVFydQbImVzmXOs4iJabcG4pRr2oqErGKBYPzsnQfN5J/OdGURmb5A4TllTUUzaIauOJl73UTivUNt8ii+odK0morM26VvHOwVIUjPzK9zwz6rwCRIwoNApGtHBQeJnO1TQ+iD4z2y+59QU1/p/boaDuqwcdHXSf63Tco+DJS9jJXWTPAHyYrJO9nsm2quIm5tDR2ZHGpFHiiwo/kPhA61xpstPFOkIdjPP4+Tk+dy0YtNKkM7BvzgFV71bTKft7RLOA3AtQQqMgZf/FBWDUBrgGF1tcGiRHYLAXP8BvoOc3splPtJY8NmyAdzRiKxbLYbcs3+dpUQUyQjZf8coUzdUvn6BozZsTSqhoIyx51AqnsA=
x-ms-exchange-antispam-messagedata: yZn98T9AqmWDiAJXCXxi+C6s1ALcNLE0vPTSetXnpzk7R9NgB1W6UGiNWiB2pD3KfCO2NHlQn70G9L1iDpnhSKXdalgIupAsjNtb3kuOuUeAVHggpGq18JLMQQUsBnx5W0ChRuo3xtqxvm9HxCmRXA==
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_CO6PR02MB76038D3A73C42781CC2D3DE2EE229CO6PR02MB7603namp_"
MIME-Version: 1.0
X-OriginatorOrg: hotmail.com
X-MS-Exchange-CrossTenant-AuthAs: Anonymous
X-MS-Exchange-CrossTenant-AuthSource: DM6NAM11FT026.eop-nam11.prod.protection.outlook.com
X-MS-Exchange-CrossTenant-RMS-PersistedConsumerOrg: 00000000-0000-0000-0000-000000000000
X-MS-Exchange-CrossTenant-Network-Message-Id: 61231480-6ecd-49f6-18b9-08d92215c658
X-MS-Exchange-CrossTenant-originalarrivaltime: 28 May 2021 20:18:36.5950 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Internet
X-MS-Exchange-CrossTenant-id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa
X-MS-Exchange-CrossTenant-rms-persistedconsumerorg: 00000000-0000-0000-0000-000000000000
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM6NAM11HT175
Archived-At: <https://mailarchive.ietf.org/arch/msg/sipcore/AeFSa8HcHfZjJOV2hifmfk8v7_U>
X-Mailman-Approved-At: Mon, 31 May 2021 06:51:23 -0700
Subject: Re: [sipcore] RFC 4028 UAS behavior requirement of Require header
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: Fri, 28 May 2021 20:18:44 -0000

--_000_CO6PR02MB76038D3A73C42781CC2D3DE2EE229CO6PR02MB7603namp_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi Ranjit, thanks for taking a look.

However, I'm more interested in case where UAS is responding to UAC's reque=
st with refresher as itself (uac).  Consider this case -

UAC ---- INVITE (Session-Expires: 1800;refresher=3Duac, Supported: timer) -=
---> UAS
UAC <---- 200 OK (Session-Expires: 1800;refresher=3Duac) ------------------=
--- UAS

In this case, the statement in question seems to convey that UAS should als=
o add "Require: timer" in its 200 response.  Why would this be, when it's c=
lear that UAC declared itself as the refresher and that timer is supported?

For reference, RFC 4028 Section 9 UAS Behavior (or page 16)
If the refresher parameter in the Session-Expires header field in the 2xx r=
esponse has a value of 'uac', the UAS MUST place a Require header field int=
o the response with the value 'timer'.

Thanks,
Hoil

________________________________
From: Ranjit Avasarala <ranjitkav12@gmail.com>
Sent: Friday, May 28, 2021 12:38 PM
To: Hoil Choi <hoil.choi@hotmail.com>; Sip-implementors@lists.cs.columbia.e=
du <Sip-implementors@lists.cs.columbia.edu>
Cc: sipcore@ietf.org <sipcore@ietf.org>
Subject: Re: [sipcore] RFC 4028 UAS behavior requirement of Require header

Hi Holi
the presence of the "Require" header with value "timer" from UAS indicates =
to UAC that it (UAC) is performing the refreshing operation. but if the UAS=
 is the refresher, then if Require header with value "timer" is present in =
response from UAS, then UAC should send BYE if it does not receive a sessio=
n refresh request from UAS.

Regards
Ranjit



On Fri, May 28, 2021 at 10:02 AM Hoil Choi <hoil.choi@hotmail.com<mailto:ho=
il.choi@hotmail.com>> wrote:
Hello,

I hope this mail finds appropriate person or team for an answer to my quest=
ion on RFC 4028.
I am a SIP enthusiast and always learning a lot about it, but by no means a=
m I an expert; so please excuse my ignorance.

I came across an interesting statement In Section 9 UAS Behavior (or page 1=
6).


If the refresher parameter in the Session-Expires header field in the
   2xx response has a value of 'uac', the UAS MUST place a Require
   header field into the response with the value 'timer'.

Statement seems to convey that UAS must place a Require header with value '=
timer' when UAC requests itself to be the refresher.

However, this statement should only be true, if UAC did not put Session-Exp=
ire with value of 'uac'.

If UAC, in INVITE request, put Session-Expire with value of 'uac' (itself),=
 UAS should not bother putting Require header field in the response.  Or to=
 be more accurate, UAC should include 'timer' in Supported header, so that =
UAS doesn't have to bother putting Require header field.

What is the reason behind the requirement of Require header, from UAS in th=
is case?

Thanks!
Hoil Choi
253-273-5442

_______________________________________________
sipcore mailing list
sipcore@ietf.org<mailto:sipcore@ietf.org>
https://www.ietf.org/mailman/listinfo/sipcore<https://na01.safelinks.protec=
tion.outlook.com/?url=3Dhttps%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2Fs=
ipcore&data=3D04%7C01%7C%7C4f68f91aa77847f0fb6508d922102eb4%7C84df9e7fe9f64=
0afb435aaaaaaaaaaaa%7C1%7C0%7C637578275155641932%7CUnknown%7CTWFpbGZsb3d8ey=
JWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sda=
ta=3D3McfrKwjz9RwC%2FBRLtdyopgzmNmUqsAKdAXyyRvChuc%3D&reserved=3D0>

--_000_CO6PR02MB76038D3A73C42781CC2D3DE2EE229CO6PR02MB7603namp_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-=
1">
<style type=3D"text/css" style=3D"display:none;"> P {margin-top:0;margin-bo=
ttom:0;} </style>
</head>
<body dir=3D"ltr">
<div style=3D"font-family: Calibri, Helvetica, sans-serif; font-size: 12pt;=
 color: rgb(0, 0, 0);">
Hi Ranjit, thanks&nbsp;for taking a look. &nbsp;</div>
<div style=3D"font-family: Calibri, Helvetica, sans-serif; font-size: 12pt;=
 color: rgb(0, 0, 0);">
<br>
</div>
<div style=3D"font-family: Calibri, Helvetica, sans-serif; font-size: 12pt;=
 color: rgb(0, 0, 0);">
However, I'm more interested in case where UAS is responding to UAC's reque=
st with refresher as itself (uac). &nbsp;Consider this case -&nbsp;</div>
<div style=3D"font-family: Calibri, Helvetica, sans-serif; font-size: 12pt;=
 color: rgb(0, 0, 0);">
<br>
</div>
<div style=3D"font-family: Calibri, Helvetica, sans-serif; font-size: 12pt;=
 color: rgb(0, 0, 0);">
UAC ---- INVITE (<span style=3D"font-size: 9pt;">Session-Expires: 1800;refr=
esher=3Duac</span><span style=3D"font-size: 9pt;">,
</span><span style=3D"font-size: 9pt;">Supported: timer</span>) ----&gt; UA=
S</div>
<div style=3D"font-family: Calibri, Helvetica, sans-serif; font-size: 12pt;=
 color: rgb(0, 0, 0);">
UAC &lt;---- 200 OK (<span style=3D"caret-color: rgb(0, 0, 0); background-c=
olor: rgb(255, 255, 255); display: inline !important; font-size: 9pt;">Sess=
ion-Expires: 1800;refresher=3Duac</span><span style=3D"caret-color:rgb(0, 0=
, 0);background-color:rgb(255, 255, 255);display:inline !important">)
 --------------------- UAS</span></div>
<div style=3D"font-family: Calibri, Helvetica, sans-serif; font-size: 12pt;=
 color: rgb(0, 0, 0);">
<span style=3D"caret-color:rgb(0, 0, 0);background-color:rgb(255, 255, 255)=
;display:inline !important"><br>
</span></div>
<div style=3D"font-family: Calibri, Helvetica, sans-serif; font-size: 12pt;=
 color: rgb(0, 0, 0);">
<span style=3D"caret-color:rgb(0, 0, 0);background-color:rgb(255, 255, 255)=
;display:inline !important">In this case, the statement in question seems t=
o convey that UAS should also add &quot;Require: timer&quot; in its 200 res=
ponse. &nbsp;Why would this be, when it's clear that
 UAC declared itself as the refresher and that timer is supported? &nbsp;</=
span></div>
<div style=3D"font-family: Calibri, Helvetica, sans-serif; font-size: 12pt;=
 color: rgb(0, 0, 0);">
<span style=3D"caret-color:rgb(0, 0, 0);background-color:rgb(255, 255, 255)=
;display:inline !important"><br>
</span></div>
<div style=3D"font-family: Calibri, Helvetica, sans-serif; font-size: 12pt;=
 color: rgb(0, 0, 0);">
<span style=3D"caret-color:rgb(0, 0, 0);background-color:rgb(255, 255, 255)=
;display:inline !important">For reference, RFC 4028&nbsp;<span style=3D"car=
et-color:rgb(0, 0, 0);background-color:rgb(255, 255, 255);display:inline !i=
mportant">Section 9 UAS Behavior (or page
 16)</span></span></div>
<div style=3D"font-family: Calibri, Helvetica, sans-serif; font-size: 12pt;=
 color: rgb(0, 0, 0);">
<span style=3D"caret-color:rgb(0, 0, 0);background-color:rgb(255, 255, 255)=
;display:inline !important"><span style=3D"caret-color:rgb(0, 0, 0);font-fa=
mily:monospace;font-size:13.33329963684082px;background-color:rgb(255, 255,=
 255);display:inline !important">If
 the refresher parameter in the Session-Expires header field in the 2xx res=
ponse has a value of 'uac', the UAS MUST place a Require header field into =
the response with the value 'timer'.
</span><br>
</span></div>
<div style=3D"font-family: Calibri, Helvetica, sans-serif; font-size: 12pt;=
 color: rgb(0, 0, 0);">
<br>
</div>
<div style=3D"font-family: Calibri, Helvetica, sans-serif; font-size: 12pt;=
 color: rgb(0, 0, 0);">
<span style=3D"caret-color:rgb(0, 0, 0);background-color:rgb(255, 255, 255)=
;display:inline !important">Thanks,</span></div>
<div style=3D"font-family: Calibri, Helvetica, sans-serif; font-size: 12pt;=
 color: rgb(0, 0, 0);">
<span style=3D"caret-color:rgb(0, 0, 0);background-color:rgb(255, 255, 255)=
;display:inline !important">Hoil</span></div>
<div>
<div id=3D"appendonsend"></div>
<div style=3D"font-family:Calibri,Helvetica,sans-serif; font-size:12pt; col=
or:rgb(0,0,0)">
<br>
</div>
<hr tabindex=3D"-1" style=3D"display:inline-block; width:98%">
<div id=3D"divRplyFwdMsg" dir=3D"ltr"><font face=3D"Calibri, sans-serif" co=
lor=3D"#000000" style=3D"font-size:11pt"><b>From:</b> Ranjit Avasarala &lt;=
ranjitkav12@gmail.com&gt;<br>
<b>Sent:</b> Friday, May 28, 2021 12:38 PM<br>
<b>To:</b> Hoil Choi &lt;hoil.choi@hotmail.com&gt;; Sip-implementors@lists.=
cs.columbia.edu &lt;Sip-implementors@lists.cs.columbia.edu&gt;<br>
<b>Cc:</b> sipcore@ietf.org &lt;sipcore@ietf.org&gt;<br>
<b>Subject:</b> Re: [sipcore] RFC 4028 UAS behavior requirement of Require =
header</font>
<div>&nbsp;</div>
</div>
<div>
<div dir=3D"ltr">Hi Holi
<div>the presence of the &quot;Require&quot; header with value &quot;timer&=
quot; from UAS indicates to UAC that it (UAC) is performing the refreshing =
operation. but if the UAS is the refresher, then if Require header with val=
ue &quot;timer&quot; is present in response from UAS, then UAC
 should send BYE if it does not receive a session refresh request from UAS.=
</div>
<div><br>
</div>
<div>Regards</div>
<div>Ranjit</div>
<div><br>
</div>
<div><br>
</div>
</div>
<br>
<div class=3D"x_gmail_quote">
<div dir=3D"ltr" class=3D"x_gmail_attr">On Fri, May 28, 2021 at 10:02 AM Ho=
il Choi &lt;<a href=3D"mailto:hoil.choi@hotmail.com">hoil.choi@hotmail.com<=
/a>&gt; wrote:<br>
</div>
<blockquote class=3D"x_gmail_quote" style=3D"margin:0px 0px 0px 0.8ex; bord=
er-left:1px solid rgb(204,204,204); padding-left:1ex">
<div dir=3D"ltr">
<div style=3D"font-family:Calibri,Helvetica,sans-serif; font-size:12pt; col=
or:rgb(0,0,0)">
Hello,&nbsp;</div>
<div style=3D"font-family:Calibri,Helvetica,sans-serif; font-size:12pt; col=
or:rgb(0,0,0)">
<br>
</div>
<div style=3D"font-family:Calibri,Helvetica,sans-serif; font-size:12pt; col=
or:rgb(0,0,0)">
I hope this mail finds appropriate person or team for an answer to my quest=
ion on RFC 4028.&nbsp;</div>
<div style=3D"font-family:Calibri,Helvetica,sans-serif; font-size:12pt; col=
or:rgb(0,0,0)">
I am a SIP enthusiast and always learning a lot about it, but by no means a=
m I an expert; so please excuse my ignorance. &nbsp;</div>
<div style=3D"font-family:Calibri,Helvetica,sans-serif; font-size:12pt; col=
or:rgb(0,0,0)">
<br>
</div>
<div style=3D"font-family:Calibri,Helvetica,sans-serif; font-size:12pt; col=
or:rgb(0,0,0)">
I came across an interesting statement In Section 9 UAS Behavior (or page 1=
6).</div>
<div style=3D"font-family:Calibri,Helvetica,sans-serif; font-size:12pt; col=
or:rgb(0,0,0)">
<pre style=3D"font-weight:400; font-size:13.3333px; margin-top:0px; margin-=
bottom:0px; break-before:page"><br></pre>
<pre style=3D"font-weight:400; font-size:13.3333px; margin-top:0px; margin-=
bottom:0px; break-before:page">If the refresher parameter in the Session-Ex=
pires header field in the=0A=
&nbsp; &nbsp;2xx response has a value of 'uac', the UAS MUST place a Requir=
e=0A=
&nbsp; &nbsp;header field into the response with the value 'timer'. </pre>
<br>
</div>
<div style=3D"font-family:Calibri,Helvetica,sans-serif; font-size:12pt; col=
or:rgb(0,0,0)">
Statement seems to convey that UAS must place a Require header with value '=
timer' when UAC requests itself to be the refresher. &nbsp;</div>
<div style=3D"font-family:Calibri,Helvetica,sans-serif; font-size:12pt; col=
or:rgb(0,0,0)">
<br>
</div>
<div style=3D"font-family:Calibri,Helvetica,sans-serif; font-size:12pt; col=
or:rgb(0,0,0)">
However, this statement should only be true, if UAC did not put Session-Exp=
ire with value of 'uac'. &nbsp;</div>
<div style=3D"font-family:Calibri,Helvetica,sans-serif; font-size:12pt; col=
or:rgb(0,0,0)">
<br>
</div>
<div style=3D"font-family:Calibri,Helvetica,sans-serif; font-size:12pt; col=
or:rgb(0,0,0)">
If UAC, in INVITE request, put Session-Expire with value of 'uac' (itself),=
 UAS should not bother putting Require header field in the response.&nbsp; =
Or to be more accurate, UAC should include 'timer' in Supported header, so =
that UAS doesn't have to bother putting
 Require header field. &nbsp;</div>
<div style=3D"font-family:Calibri,Helvetica,sans-serif; font-size:12pt; col=
or:rgb(0,0,0)">
<br>
</div>
<div style=3D"font-family:Calibri,Helvetica,sans-serif; font-size:12pt; col=
or:rgb(0,0,0)">
What is the reason behind the requirement of Require header, from UAS in th=
is case?</div>
<div style=3D"font-family:Calibri,Helvetica,sans-serif; font-size:12pt; col=
or:rgb(0,0,0)">
<br>
</div>
<div style=3D"font-family:Calibri,Helvetica,sans-serif; font-size:12pt; col=
or:rgb(0,0,0)">
Thanks!</div>
<div style=3D"font-family:Calibri,Helvetica,sans-serif; font-size:12pt; col=
or:rgb(0,0,0)">
Hoil Choi</div>
<div style=3D"font-family:Calibri,Helvetica,sans-serif; font-size:12pt; col=
or:rgb(0,0,0)">
253-273-5442</div>
<div style=3D"font-family:Calibri,Helvetica,sans-serif; font-size:12pt; col=
or:rgb(0,0,0)">
<br>
</div>
</div>
_______________________________________________<br>
sipcore mailing list<br>
<a href=3D"mailto:sipcore@ietf.org" target=3D"_blank">sipcore@ietf.org</a><=
br>
<a href=3D"https://na01.safelinks.protection.outlook.com/?url=3Dhttps%3A%2F=
%2Fwww.ietf.org%2Fmailman%2Flistinfo%2Fsipcore&amp;data=3D04%7C01%7C%7C4f68=
f91aa77847f0fb6508d922102eb4%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C6=
37578275155641932%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luM=
zIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&amp;sdata=3D3McfrKwjz9RwC%2FBRLtdy=
opgzmNmUqsAKdAXyyRvChuc%3D&amp;reserved=3D0" originalsrc=3D"https://www.iet=
f.org/mailman/listinfo/sipcore" shash=3D"OiIuEiXMs9jVul/tgmBirmTnH3tQWZrjaj=
rDYkjCG9lWdT+CVWNulvt0UEi7dbW3nFoXu18wpvM7uiMMiq2HB+bhafnJ4TUNKGo+QJ2AFt8Al=
o+ZFvnTToSw8vFU1kCud/dysCd4VL7nDgHwbPINA1zOtx8xcLrGC2bYNfvxUJI=3D" rel=3D"n=
oreferrer" target=3D"_blank">https://www.ietf.org/mailman/listinfo/sipcore<=
/a><br>
</blockquote>
</div>
</div>
</div>
</body>
</html>

--_000_CO6PR02MB76038D3A73C42781CC2D3DE2EE229CO6PR02MB7603namp_--

