IETF Logo Mail Archive

Re: [sipcore] Session Timers (RFC 4028) for REFER, PUBLISH, MESSAGE not defined

Paul Kyzivat <pkyzivat@alum.mit.edu> Sun, 10 May 2020 17:00 UTC

Return-Path: <pkyzivat@alum.mit.edu>
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 B161C3A0A9F for <sipcore@ietfa.amsl.com>; Sun, 10 May 2020 10:00:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.991
X-Spam-Level:
X-Spam-Status: No, score=-1.991 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_MSPIKE_H2=-0.001, T_SPF_PERMERROR=0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=alum.mit.edu
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 SHeAAuydmcVC for <sipcore@ietfa.amsl.com>; Sun, 10 May 2020 10:00:00 -0700 (PDT)
Received: from NAM04-CO1-obe.outbound.protection.outlook.com (mail-eopbgr690047.outbound.protection.outlook.com [40.107.69.47]) (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 AC9A73A0AA3 for <sipcore@ietf.org>; Sun, 10 May 2020 10:00:00 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=mOKnwf4Q32U49+sJVEO+NCzLzALcSHdsVMjxUL2FIwoQrYTMSCrfvH3nU17dx9S3gvnn8WI4jCppZaKsZ/fQUnR2h/D0LVDM7PjeTeG893Ojn/33lsq9r4WME/j0HuDREaAc4LGdybBVRyziY/hb4sdrWb9u1HC/JkD3I7w01GwVzupA5mtS3YhBVVfxVzgVU6wivdOASGEgx2QIqd+QV64uqHFvnEfpstt4DLTtCgM3REz8x1he7K11Je4eicaahAbJEaoYZrhCgyizVxR2LKHVcfmLIKTO8r2RG1OWopp8ZfzEzgCLhptUsF4g+tMWncMILfjgtSAKY0C+d1B0JA==
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=lYSwJchWGLx2vdjtt0fblQONgjNRwdM1KR9kutfeCAk=; b=oHL3FTKXndAqkg3/XLl/80xyI3BLT2ohesC21VCDjHrjo4kFVjUana6waq3i/NVFiB7PkLYC4cIpjQE7XTuHBD8bXRS3opPa2Z3Om4QOyCW/LIduPny/QgSsjSDBRTW1Y6xXo0YVxLyqlc4Kh3sh+3pjboP/snCGd2mm1LoEereThN5AvioQZjiilaQYNcNNxIfe626PQxOUBaVwman8jnCaUS+tksLOQSUF5yVL7+H6d4wOCH3/peeXLmPJ620wfJYQmBo+m+4dKDmfE8uS7QOU986nT56p8VGbd6xVnGTegYxvoyXFW21k9XJSZs3D29Yom/Hy2FuYOfZaFyy4/A==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=permerror (sender ip is 18.7.68.33) smtp.rcpttodomain=ietf.org smtp.mailfrom=alum.mit.edu; dmarc=none action=none header.from=alum.mit.edu; dkim=none (message not signed); arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=alum.mit.edu; s=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=lYSwJchWGLx2vdjtt0fblQONgjNRwdM1KR9kutfeCAk=; b=d31RJSv9T38hQziM/3m5f51w5NjvyW9EbOmaySnDv5oPauKw4WpogVUVGSyPcN+QU2QHLsZaO68vXvBaED5vg/eA3t4q9tws9iFzvHCa51mCy7AmZV6WWZ/cLBPGe1yLnYubuyX25sZLbTq9WHs3unLcPAsxYrQ68Nt5pCKYryQ=
Received: from BL0PR05CA0016.namprd05.prod.outlook.com (2603:10b6:208:91::26) by DM6PR12MB2666.namprd12.prod.outlook.com (2603:10b6:5:4d::11) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2979.35; Sun, 10 May 2020 16:59:58 +0000
Received: from BL2NAM02FT019.eop-nam02.prod.protection.outlook.com (2603:10b6:208:91:cafe::16) by BL0PR05CA0016.outlook.office365.com (2603:10b6:208:91::26) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3000.11 via Frontend Transport; Sun, 10 May 2020 16:59:58 +0000
Authentication-Results: spf=permerror (sender IP is 18.7.68.33) smtp.mailfrom=alum.mit.edu; ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=none action=none header.from=alum.mit.edu;
Received-SPF: PermError (protection.outlook.com: domain of alum.mit.edu used an invalid SPF mechanism)
Received: from outgoing-alum.mit.edu (18.7.68.33) by BL2NAM02FT019.mail.protection.outlook.com (10.152.77.166) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2979.29 via Frontend Transport; Sun, 10 May 2020 16:59:57 +0000
Received: from Kokiri.localdomain (c-24-62-227-142.hsd1.ma.comcast.net [24.62.227.142]) (authenticated bits=0) (User authenticated as pkyzivat@ALUM.MIT.EDU) by outgoing-alum.mit.edu (8.14.7/8.12.4) with ESMTP id 04AGxtKK001537 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT) for <sipcore@ietf.org>; Sun, 10 May 2020 12:59:57 -0400
To: sipcore@ietf.org
References: <20200510131235.8E2A6C0171@smtp.hushmail.com>
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
Message-ID: <854d7cef-03eb-8974-9159-c493df015996@alum.mit.edu>
Date: Sun, 10 May 2020 12:59:55 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:68.0) Gecko/20100101 Thunderbird/68.7.0
MIME-Version: 1.0
In-Reply-To: <20200510131235.8E2A6C0171@smtp.hushmail.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 8bit
X-EOPAttributedMessage: 0
X-Forefront-Antispam-Report: CIP:18.7.68.33; CTRY:US; LANG:en; SCL:1; SRV:; IPV:CAL; SFV:NSPM; H:outgoing-alum.mit.edu; PTR:outgoing-alum.mit.edu; CAT:NONE; SFTY:; SFS:(136003)(396003)(39860400002)(376002)(346002)(46966005)(33430700001)(53546011)(956004)(2616005)(75432002)(356005)(316002)(786003)(36906005)(478600001)(82310400002)(33440700001)(7596003)(186003)(70586007)(26005)(15650500001)(6916009)(31696002)(70206006)(82740400003)(8676002)(336012)(2906002)(5660300002)(47076004)(86362001)(8936002)(31686004)(43740500002); DIR:OUT; SFP:1101;
X-MS-PublicTrafficType: Email
X-MS-Office365-Filtering-Correlation-Id: 7715aec4-bcd8-40da-8658-08d7f50391eb
X-MS-TrafficTypeDiagnostic: DM6PR12MB2666:
X-Microsoft-Antispam-PRVS: <DM6PR12MB26668727D2120BB0FD0FEBE1F9A00@DM6PR12MB2666.namprd12.prod.outlook.com>
X-MS-Oob-TLC-OOBClassifiers: OLM:8273;
X-Forefront-PRVS: 039975700A
X-MS-Exchange-SenderADCheck: 1
X-Microsoft-Antispam: BCL:0;
X-Microsoft-Antispam-Message-Info: o5HzdYl3gzC+3JXox1ry0fEJ2nnZfBBYvTfas8oas4xUbX0/EtESRTFasp0LYZhP1+gPCyhl/hECtzuqzKeA27d5mMoAF3J7DabeuxZiYmGKOeF1Cuk6mOJk1Q/2gLGqbxMFB/Di2+T410vYY/NyZKfKet+NH3zncJVhQj/3rzgjDPSLFsbZF+Q5BUabq1FqcLDymJRKMQ1DQxL42kNynzAKEg/nBk1jSgtfGqGlKVV9vI/MfcthtnM2FlZVnhA5Q65OCCk2Rv+MSA8jrZX4MCvO5yzazHaYmFh8o+3la9L59pi2Wk+0Y9qRFKS4DpJcxqTEsOKox8gtaD2l87/UjsoKgrqfGdAKrwn7Uu9G0iRBccJW5797j4zm9rilZMWR7ViPvF1N19HzqtSIfwl8WO11MmwPI4O1vPescfUlpENjeSTJpsID0JTUvOSJZjXG+W5rGXE1a9kdkOS4CLEv1BI9Hfw0Ouh4uMdlM/CdXjGzP4cZsI4c3R311F4giVoJoggvq9N7xgAb3/QNNkUzTtYnsJ/DuluiE2TnwDWIGXNARiR3Bf4rk5780OY4spxv5gOAyCAKfZvvicd7PmEdOCGakMOkiCu0utGBDy2IMUw=
X-OriginatorOrg: alum.mit.edu
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 10 May 2020 16:59:57.7483 (UTC)
X-MS-Exchange-CrossTenant-Network-Message-Id: 7715aec4-bcd8-40da-8658-08d7f50391eb
X-MS-Exchange-CrossTenant-Id: 3326b102-c043-408b-a990-b89e477d582f
X-MS-Exchange-CrossTenant-OriginalAttributedTenantConnectingIp: TenantId=3326b102-c043-408b-a990-b89e477d582f; Ip=[18.7.68.33]; Helo=[outgoing-alum.mit.edu]
X-MS-Exchange-CrossTenant-FromEntityHeader: HybridOnPrem
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM6PR12MB2666
Archived-At: <https://mailarchive.ietf.org/arch/msg/sipcore/l4Y_eNAYuP6c83m4cjFYaaslvB4>
Subject: Re: [sipcore] Session Timers (RFC 4028) for REFER, PUBLISH, MESSAGE not defined
X-BeenThere: sipcore@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: SIP Core Working Group <sipcore.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sipcore>, <mailto:sipcore-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sipcore/>
List-Post: <mailto:sipcore@ietf.org>
List-Help: <mailto:sipcore-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sipcore>, <mailto:sipcore-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 10 May 2020 17:00:03 -0000

On 5/10/20 9:12 AM, Samir Srivastava wrote:
> Hi,
> 
>    The table mentioned in Section 4 in RFC 4028 does not contain entries 
> for REFER, PUBLISH and MESSAGE methods Below is the table from Section 4
> 
> 
>     +---------------+-----+-----+---+---+---+---+---+---+---+---+---+---+
>     |     Header    |where|proxy|ACK|BYE|CAN|INV|OPT|REG|PRA|UPD|SUB|NOT|
>     +---------------+-----+-----+---+---+---+---+---+---+---+---+---+---+
>     |Session-Expires|  R  | amr | - | - | - | o | - | - | - | o | - | - |
>     |               |     |     |   |   |   |   |   |   |   |   |   |   |
>     |Session-Expires| 2xx | ar  | - | - | - | o | - | - | - | o | - | - |
>     |               |     |     |   |   |   |   |   |   |   |   |   |   |
>     |Min-SE         |  R  | amr | - | - | - | o | - | - | - | o | - | - |
>     |               |     |     |   |   |   |   |   |   |   |   |   |   |
>     |Min-SE         | 422 |     | - | - | - | m | - | - | - | m | - | - |
>     +---------------+-----+-----+---+---+---+---+---+---+---+---+---+---+
> 
>    They are not applicable for these, but it would have been better if 
> it is said categorically.

IIRC, quite a long time ago it was decided that this table in 3261 was a 
bad idea, because it is essentially a summary of normative language in 
other sections of the document and is necessarily an approximation.

After that, other work that updates and extends 3261 has been 
inconsistent it whether it updates the table or not.

What we should be careful of is that the in progress update to session 
timers is clear, normatively and expositively,  one way or another.

	Thanks,
	Paul

v2.23.0 | Report a Bug | By Email