
From nobody Mon Jan  3 00:38:50 2022
Return-Path: <oej@edvina.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 20B153A0B32 for <sipcore@ietfa.amsl.com>; Mon,  3 Jan 2022 00:38:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level: 
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, 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 Fc7YnF_5Vgws for <sipcore@ietfa.amsl.com>; Mon,  3 Jan 2022 00:38:44 -0800 (PST)
Received: from smtp7.webway.se (smtp7.webway.se [IPv6:2a02:920:212e::205]) (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 6C6FC3A0CBE for <sipcore@ietf.org>; Mon,  3 Jan 2022 00:38:42 -0800 (PST)
Received: from smtpclient.apple (h-176-10-205-12.A165.corp.bahnhof.se [176.10.205.12]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp7.webway.se (Postfix) with ESMTPSA id 68427216E; Mon,  3 Jan 2022 09:38:37 +0100 (CET)
From: "Olle E. Johansson" <oej@edvina.net>
Content-Type: multipart/alternative; boundary="Apple-Mail=_22D19BF7-6456-41F1-84EE-F5C09DD1D4DC"
Mime-Version: 1.0 (Mac OS X Mail 15.0 \(3693.40.0.1.81\))
Date: Mon, 3 Jan 2022 09:38:36 +0100
References: <DABC5259-B69C-4F6F-8110-C61B40198A76@mnot.net>
Cc: Mark Nottingham <mnot@mnot.net>
To: sipcore@ietf.org
Message-Id: <ECADE976-69B6-4ACF-8BCE-18276FB52EDC@edvina.net>
X-Mailer: Apple Mail (2.3693.40.0.1.81)
Archived-At: <https://mailarchive.ietf.org/arch/msg/sipcore/5xgWuuBTGTH_Cbl0wE3WXNEyNJw>
Subject: [sipcore] Fwd: [art] RFC2817, IPP, and XCAP
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, 03 Jan 2022 08:38:49 -0000

--Apple-Mail=_22D19BF7-6456-41F1-84EE-F5C09DD1D4DC
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Mark asked a question that relates to XCAP in the ART mailing list. =
Forwarding to SIPcore as I suspect there are many more people interested =
in XCAP on this mailing list.

Happy new SIP year everyone!

/O

> Begin forwarded message:
>=20
> From: Mark Nottingham <mnot@mnot.net>
> Subject: [art] RFC2817, IPP, and XCAP
> Date: 3 January 2022 at 07:24:42 CET
> To: art@ietf.org
>=20
> Happy New Year, ART folks.
>=20
> I'm looking into whether we can move RFC2817 to Historic, because for =
HTTP's purposes, the bits we actually use have moved into the Semantics =
document.
>=20
> However, I notice that RFC8010 still specifies the Upgrade mechanism =
for 'ipp' URLs. Can anyone from the IPP community speak as to whether =
that's actually in use?
>=20
> There's a similar question regarding RFC4825 and XCAP.
>=20
> If the damage caused by moving it to Historic would be too great, I =
might try to spin up a short applicability note that explained which =
bits moved into semantics, and that what's left is only usable if a =
protocol using HTTP explicitly opts into it (like IPP).
>=20
> Cheers,
>=20
>=20
> --
> Mark Nottingham   https://www.mnot.net/
>=20
> _______________________________________________
> art mailing list
> art@ietf.org
> https://www.ietf.org/mailman/listinfo/art


--Apple-Mail=_22D19BF7-6456-41F1-84EE-F5C09DD1D4DC
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"">Mark =
asked a question that relates to XCAP in the ART mailing list. =
Forwarding to SIPcore as I suspect there are many more people interested =
in XCAP on this mailing list.<div class=3D""><br class=3D""></div><div =
class=3D"">Happy new SIP year everyone!</div><div class=3D""><br =
class=3D""></div><div class=3D"">/O<br class=3D""><div><br =
class=3D""><blockquote type=3D"cite" class=3D""><div class=3D"">Begin =
forwarded message:</div><br class=3D"Apple-interchange-newline"><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px;" class=3D""><span style=3D"font-family: =
-webkit-system-font, Helvetica Neue, Helvetica, sans-serif; =
color:rgba(0, 0, 0, 1.0);" class=3D""><b class=3D"">From: =
</b></span><span style=3D"font-family: -webkit-system-font, Helvetica =
Neue, Helvetica, sans-serif;" class=3D"">Mark Nottingham &lt;<a =
href=3D"mailto:mnot@mnot.net" class=3D"">mnot@mnot.net</a>&gt;<br =
class=3D""></span></div><div style=3D"margin-top: 0px; margin-right: =
0px; margin-bottom: 0px; margin-left: 0px;" class=3D""><span =
style=3D"font-family: -webkit-system-font, Helvetica Neue, Helvetica, =
sans-serif; color:rgba(0, 0, 0, 1.0);" class=3D""><b class=3D"">Subject: =
</b></span><span style=3D"font-family: -webkit-system-font, Helvetica =
Neue, Helvetica, sans-serif;" class=3D""><b class=3D"">[art] RFC2817, =
IPP, and XCAP</b><br class=3D""></span></div><div style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px;" =
class=3D""><span style=3D"font-family: -webkit-system-font, Helvetica =
Neue, Helvetica, sans-serif; color:rgba(0, 0, 0, 1.0);" class=3D""><b =
class=3D"">Date: </b></span><span style=3D"font-family: =
-webkit-system-font, Helvetica Neue, Helvetica, sans-serif;" class=3D"">3 =
January 2022 at 07:24:42 CET<br class=3D""></span></div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px;" class=3D""><span style=3D"font-family: =
-webkit-system-font, Helvetica Neue, Helvetica, sans-serif; =
color:rgba(0, 0, 0, 1.0);" class=3D""><b class=3D"">To: </b></span><span =
style=3D"font-family: -webkit-system-font, Helvetica Neue, Helvetica, =
sans-serif;" class=3D""><a href=3D"mailto:art@ietf.org" =
class=3D"">art@ietf.org</a><br class=3D""></span></div><br class=3D""><div=
 class=3D""><div class=3D"">Happy New Year, ART folks.<br class=3D""><br =
class=3D"">I'm looking into whether we can move RFC2817 to Historic, =
because for HTTP's purposes, the bits we actually use have moved into =
the Semantics document.<br class=3D""><br class=3D"">However, I notice =
that RFC8010 still specifies the Upgrade mechanism for 'ipp' URLs. Can =
anyone from the IPP community speak as to whether that's actually in =
use?<br class=3D""><br class=3D"">There's a similar question regarding =
RFC4825 and XCAP.<br class=3D""><br class=3D"">If the damage caused by =
moving it to Historic would be too great, I might try to spin up a short =
applicability note that explained which bits moved into semantics, and =
that what's left is only usable if a protocol using HTTP explicitly opts =
into it (like IPP).<br class=3D""><br class=3D"">Cheers,<br class=3D""><br=
 class=3D""><br class=3D"">--<br class=3D"">Mark Nottingham =
&nbsp;&nbsp;<a href=3D"https://www.mnot.net/" =
class=3D"">https://www.mnot.net/</a><br class=3D""><br =
class=3D"">_______________________________________________<br =
class=3D"">art mailing list<br class=3D""><a href=3D"mailto:art@ietf.org" =
class=3D"">art@ietf.org</a><br =
class=3D"">https://www.ietf.org/mailman/listinfo/art<br =
class=3D""></div></div></blockquote></div><br =
class=3D""></div></body></html>=

--Apple-Mail=_22D19BF7-6456-41F1-84EE-F5C09DD1D4DC--


From nobody Tue Jan  4 01:50:56 2022
Return-Path: <christer.holmberg@ericsson.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 EBEB63A1A22 for <sipcore@ietfa.amsl.com>; Tue,  4 Jan 2022 01:50:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.576
X-Spam-Level: 
X-Spam-Status: No, score=-2.576 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.576, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=0.1, 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 (1024-bit key) header.d=ericsson.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 oyyPE2kUZlRV for <sipcore@ietfa.amsl.com>; Tue,  4 Jan 2022 01:50:49 -0800 (PST)
Received: from EUR04-DB3-obe.outbound.protection.outlook.com (mail-eopbgr60041.outbound.protection.outlook.com [40.107.6.41]) (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 186C83A1A1F for <sipcore@ietf.org>; Tue,  4 Jan 2022 01:50:48 -0800 (PST)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=jm0GmHtEfh4F+JCq8ezZgOGvL4t8nYLcn25JZCD7xcwBR5jzaAD7alKb4SlUNhq17Dwb8CP7SDUinzP/amjL4hDd5O3dBwxsAyQZG7G+VIweWRgxHL19W4Y7q4+hr+ThTV05wrv1NcxVPbG6LuCQfjD8aTpuY5+xnC+9rORGxoYiO8dVwpkMUe+EnQJHJhR8JWZ949ndkdd9Fe1mcbs39P0D+AHAcqcP0mOSUSahBR7xCyLkQCtsOscphCwoD6Mq3JTgsKfLExa2XynuP4ohiTIOatrEFa0DQPxmP3vEPItkOXTtdk1Pq6JG1sCAxUV8SwIN1afkr7cY8hcdODJCcQ==
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-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=D/8oGXaom8wL32IAc/+OVBKJzVDzGwNwFER3yQA6z0A=; b=RGlWNNHfk/naiyHPiiayFCLu8yn6JtZNi0RoBN3N3/amqiquRzoLmpo9uH4F0E781vrdQrNdwbBSIt/1K8Qnpe4fdp6a+ekXiAthh3a8e7IlQsLp+me8Infy+egeb7w8fvj5lCEz3pMrT4nGnxOoJ6SRvINsy0c2k3MMTKCrSUSli2PADpCbYgDMqXdEe99pmGWAcsxrC9u6/Xfdg8Agnke2/IM2BMnrQNlPlneOkpiNy2TtJeOny9vtXD3lTfOWXwgxFeC55sSkOyFrO0l51jn1/ha9pi1Uo3ad2heQrInnPfBuPtK5dp/aTdtOnMStuSbkCilcWXyRo0jYcztkaw==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=ericsson.com; dmarc=pass action=none header.from=ericsson.com; dkim=pass header.d=ericsson.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ericsson.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=D/8oGXaom8wL32IAc/+OVBKJzVDzGwNwFER3yQA6z0A=; b=LUI7Co/UR1NNWIE19VyOYtmAKU2mST7zkk1lQ0y+kp3Z3JK6TmArPV8q2rXtmJ7wzkj1DxG3CFpX3quXSgK1yy5cDCMZpRJCOfXrM70hnak/m3yo7I3DOpj8lyoCThXI9wRLK56dF3VPLBEx0UjR3uYVt3Thye2KxphIwUC8PLk=
Received: from HE1PR07MB4441.eurprd07.prod.outlook.com (2603:10a6:7:9f::27) by DB7PR07MB5306.eurprd07.prod.outlook.com (2603:10a6:10:69::29) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.4867.6; Tue, 4 Jan 2022 09:50:45 +0000
Received: from HE1PR07MB4441.eurprd07.prod.outlook.com ([fe80::9db7:2e43:bff0:7d42]) by HE1PR07MB4441.eurprd07.prod.outlook.com ([fe80::9db7:2e43:bff0:7d42%6]) with mapi id 15.20.4867.006; Tue, 4 Jan 2022 09:50:45 +0000
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: "Olle E. Johansson" <oej@edvina.net>, "sipcore@ietf.org" <sipcore@ietf.org>
CC: Mark Nottingham <mnot@mnot.net>
Thread-Topic: [sipcore] Fwd: [art] RFC2817, IPP, and XCAP
Thread-Index: AQHYAGqtmwOPBaMzPUm6W4t4g2BUuqxQ+eZmgAGlUGU=
Date: Tue, 4 Jan 2022 09:50:45 +0000
Message-ID: <HE1PR07MB4441F094E5FAA479B3BCDA48934A9@HE1PR07MB4441.eurprd07.prod.outlook.com>
References: <DABC5259-B69C-4F6F-8110-C61B40198A76@mnot.net> <ECADE976-69B6-4ACF-8BCE-18276FB52EDC@edvina.net>
In-Reply-To: <ECADE976-69B6-4ACF-8BCE-18276FB52EDC@edvina.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: dkim=none (message not signed) header.d=none;dmarc=none action=none header.from=ericsson.com;
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: b815c474-fc7f-49ef-f51c-08d9cf67adda
x-ms-traffictypediagnostic: DB7PR07MB5306:EE_
x-microsoft-antispam-prvs: <DB7PR07MB5306D62FF116175CAA8E1634934A9@DB7PR07MB5306.eurprd07.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:8882;
x-ms-exchange-senderadcheck: 1
x-ms-exchange-antispam-relay: 0
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: uhceOpv3fVcQJESGztf51nIJ/bpZkPVQnbda2erPbDUGxc1N8yZNp+AD0/auywf65zpDP1bkDQEM8NLIWh4n3rZoMAT6k1IAIUWmDcTMA03ioIBimhzeYAQsgG+mcOu0lxJZaMLFmM26XJqj+3Z6NPmVSpH8LZc276un//WDNC1plTMY8UmZkEo9TP56vtP1ZjwYKa+KeJdn7HPV/9m81NU1SLaWhG3CpVW4fbDLPWMUVn7De2kQf/iFWyd/x3bnbdbG3IgPH63tYwsDYSnRfudAoIVs5sbYNZlDhzu/NGx+xjzDmPQ9D/rH+3hJrov4PS2eUF8DmqwG3rr+u1EXU7ubVPNvWkicY2PTJPlqZ72Gg7am4X9MsK3nFuTx/DUbao7XQCva9UCDjJ4BSICTDXhpz/PiNw+vpP3mj3DZFereGiNCuL5EIgFhSSLG9PFoC8OaTVuu2IGx1nZyqzTCjVQgMBpJeJYFaaQ8s/Q62FjQYRzNmvKDk+ZOuIOg27XaHE1COOYXl5rzoBexyxC77jMyBPxkHpf1DtZ2CF7i8q3FyWuBagdzXfZAB8ZP4BfvsHdph67/7tTpP9HJrcAR2FEQxDHn0uOUBdNxD4BwLuwQuL97nyfWs3CUQLn64x8VgUcB+XlkbsenZZ4ykn0o4fxK5pTqNwUjsAWx+VCRk/muhHvP1qzaeS+RRkBVkWCAahMLnjsAQbG+Jz+wPlS2pLJDJnGdAi89h0KtklVmytKEbH4Bf+0GftD9r0adKyfQ+UZji+eRdAM0TYynWxt6ccn1bkvDTvwUBMnw6okrr28=
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:;  IPV:NLI; SFV:NSPM; H:HE1PR07MB4441.eurprd07.prod.outlook.com; PTR:; CAT:NONE;  SFS:(13230001)(4636009)(366004)(76116006)(83380400001)(44832011)(2906002)(33656002)(71200400001)(86362001)(9686003)(5660300002)(64756008)(6506007)(52536014)(66446008)(186003)(110136005)(66946007)(66476007)(53546011)(66556008)(316002)(4326008)(7696005)(8936002)(8676002)(38100700002)(166002)(55016003)(508600001)(966005)(82960400001)(122000001)(38070700005)(20210929001); DIR:OUT; SFP:1101; 
x-ms-exchange-antispam-messagedata-chunkcount: 1
x-ms-exchange-antispam-messagedata-0: =?us-ascii?Q?dDvSsOwxFhZ9QFxn3v/6Jm17qk6aCAeB3vjan9Y1MN9ybOC+kncK8TDAt/U+?= =?us-ascii?Q?yhOlwZKvI5JP0U/x4GzowswKSYqJHNoJEqyMUpCyg+yfOI6NuDoohr+0BTSJ?= =?us-ascii?Q?HLjn9zo7WzjdhXNrg/ng2sdmRihOU4Q9hGHoKZLfS7P/nj0q8ve1381MU6BT?= =?us-ascii?Q?dZZL4UVguRQoKNUYbEqgTalAmbKPYlSLs4+zoS2yanUmH7bygPrVXieJhPJ2?= =?us-ascii?Q?TBvLpRSv5lM1mlfj3EckSagr7CRlbhHweEXyLn2FrOwXK944yNv1espC+o4M?= =?us-ascii?Q?raA4yd+xs8AHC+rwOiZwPsMPWxhE+ZQvEl+3voe19HQ9oHdwwOw+viAdyHeP?= =?us-ascii?Q?gKrNvJouGaS2RtYRbg863lOrgUtGtk5m+B0smZQKSbVotQwJ42np3DjfDsWn?= =?us-ascii?Q?ftMJNJFwCbLkUAB8BJs0Hr8EUyBIHEVKdyBH7r+2eHETF7vCQlOvD+ob/S7g?= =?us-ascii?Q?PmSndjuPXG9qAGNyvF8To4lsfaOuRDXnLzP0Z9CGCS05VFU6IlmukV6t2/TI?= =?us-ascii?Q?Ahd366V2Ha+iOpmQih1Fuk2hTOIXINYa378ox4IvtY0gpKnGhqhIe7YoEtu8?= =?us-ascii?Q?f64U5J9Tjy8l7QlObpnc/LjyJyKlzK9RiwOd9NxpBuIRqN19cr1bw3Bo+t6m?= =?us-ascii?Q?xLigv0wywRjE6vOL6SmXMbDx24d0VaJGJp434w8cuVLJUQJJ9EjD67Khn/9q?= =?us-ascii?Q?z2+h5x2V7CI/RVRW+X2tW4v2kHkxlMaFlxput6GWkRAI4IPudnljlpK42uan?= =?us-ascii?Q?f4WCLvEMIuvpARm4VivvYxWveLmDnYFMdMu3km6iZT+Yw2vPi9EJzjWE82UY?= =?us-ascii?Q?+LQnjg08lgJOuTOs/t+z4XgBFA4Xs0MOhRmjCLZcSFtMBvuyTG6fhVSMserE?= =?us-ascii?Q?lx5AButYUdroPRkQUkt6koYNDs1nkIg3kW5NWoWsmPK4Dn6OjXTFHljOA0vP?= =?us-ascii?Q?8TBDLyf0Pk9qRnt42TjQZZcwFwjqwCIkxFTbYRW9T7k9KmbbtgmCFCVjnEdo?= =?us-ascii?Q?zqZLheL8AyzzkINrbC854TMvScrRKFVUiRTprTJr83T38FpIF2sCvslt0vM5?= =?us-ascii?Q?2HZz3QIAa7Q/iK1x5SfozdTogT6c9HIUz8D2cU2z2t9V2PhoEm96vxVnsmV4?= =?us-ascii?Q?5rYr8+lwESZ7ocMB/PxSDvk6nlUXlu6dldoO15PhKL+iJziF/vbhfCFD0SHw?= =?us-ascii?Q?zh5UsowZcoCKK4Ced73HzX8cyQtzZ4Mtbg1z/z4Dpzop5ETiaUcz9nFl9YfA?= =?us-ascii?Q?Iz/f5xSYd7m9cAYGPt8L4bOo6cIjokxreOrVlqhpzwJ002KTz89e0jtlRDT2?= =?us-ascii?Q?gr/GRRLtp4rz4kKkkVv+fi8YFOTJXtCHlzpGiLEiydHKmhResZunhz8CYyIk?= =?us-ascii?Q?tz/OtUunVY2g2ZBywMdlsGo8JWsYSiMRg62erA+CwHz7VO4CehGsKJ9Cbr7h?= =?us-ascii?Q?G7FKsy2IpwQyJuxCC1N8x15cCUIbvIi8ZTLe4ZIeno/e4zrVpQnK0y89LuRy?= =?us-ascii?Q?zhEWkYCKA2aj+6hrwAZaxeiWrear2GCseQEZilGTEDtjcTatlcEfwj1WH+3X?= =?us-ascii?Q?33znRqWFinA1mZnrQqX41c/Y+PHP3WAcWZPleH08DkHem3TCbEPH0jNLXGWO?= =?us-ascii?Q?reHTMyb7FX8rRP1UmkC8abTzXRVrTrS5MM0DCv/GZWHtg5RoS3IYAtjhzOXc?= =?us-ascii?Q?5/BfaXzKMxxD96B+DESukvoGYnco6O9X8T20+AOYzcIDCkec9oc7HyuPNFem?= =?us-ascii?Q?SwJGXwL4FvdQM3CxB5if82/FMjdr6Mw=3D?=
Content-Type: multipart/alternative; boundary="_000_HE1PR07MB4441F094E5FAA479B3BCDA48934A9HE1PR07MB4441eurp_"
MIME-Version: 1.0
X-OriginatorOrg: ericsson.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: HE1PR07MB4441.eurprd07.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: b815c474-fc7f-49ef-f51c-08d9cf67adda
X-MS-Exchange-CrossTenant-originalarrivaltime: 04 Jan 2022 09:50:45.3775 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 92e84ceb-fbfd-47ab-be52-080c6b87953f
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: mej4RcrD0kvPaH4OwV6DQP1sVu9SvfBxGGqp8ELGkXHxE9zpKDpy9gnY4GxDE7m2uTJu/VShD1j46qozJ+kgQ/iQlnFu8mkS4r6NElrq8qo=
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DB7PR07MB5306
Archived-At: <https://mailarchive.ietf.org/arch/msg/sipcore/rvupJDrc-PWLV_m0LK7a0MsZJtI>
Subject: Re: [sipcore] Fwd: [art] RFC2817, IPP, and XCAP
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, 04 Jan 2022 09:50:54 -0000

--_000_HE1PR07MB4441F094E5FAA479B3BCDA48934A9HE1PR07MB4441eurp_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi,

Happy New Year!

I sent a reply on the ART list, informing that 3GPP references 2817, and as=
king whether the upgrade mechanism in 7230 is backward compatible with the =
one in 2817, and asking what/if will happen with the IANA registry upgrade =
value that 2817 defines.

Regards,

Christer

________________________________
From: sipcore <sipcore-bounces@ietf.org> on behalf of Olle E. Johansson <oe=
j@edvina.net>
Sent: Monday, January 3, 2022 10:39 AM
To: sipcore@ietf.org
Cc: Mark Nottingham
Subject: [sipcore] Fwd: [art] RFC2817, IPP, and XCAP

Mark asked a question that relates to XCAP in the ART mailing list. Forward=
ing to SIPcore as I suspect there are many more people interested in XCAP o=
n this mailing list.

Happy new SIP year everyone!

/O

Begin forwarded message:

From: Mark Nottingham <mnot@mnot.net<mailto:mnot@mnot.net>>
Subject: [art] RFC2817, IPP, and XCAP
Date: 3 January 2022 at 07:24:42 CET
To: art@ietf.org<mailto:art@ietf.org>

Happy New Year, ART folks.

I'm looking into whether we can move RFC2817 to Historic, because for HTTP'=
s purposes, the bits we actually use have moved into the Semantics document=
.

However, I notice that RFC8010 still specifies the Upgrade mechanism for 'i=
pp' URLs. Can anyone from the IPP community speak as to whether that's actu=
ally in use?

There's a similar question regarding RFC4825 and XCAP.

If the damage caused by moving it to Historic would be too great, I might t=
ry to spin up a short applicability note that explained which bits moved in=
to semantics, and that what's left is only usable if a protocol using HTTP =
explicitly opts into it (like IPP).

Cheers,


--
Mark Nottingham   https://www.mnot.net/<https://protect2.fireeye.com/v1/url=
?k=3D31323334-501d5122-313273af-454445555731-2328097a3e27f5ac&q=3D1&e=3D234=
99f48-e28c-427d-a8a2-23beed6af6ca&u=3Dhttps%3A%2F%2Fwww.mnot.net%2F>

_______________________________________________
art mailing list
art@ietf.org<mailto:art@ietf.org>
https://www.ietf.org/mailman/listinfo/art<https://protect2.fireeye.com/v1/u=
rl?k=3D31323334-501d5122-313273af-454445555731-6d2584570e589803&q=3D1&e=3D2=
3499f48-e28c-427d-a8a2-23beed6af6ca&u=3Dhttps%3A%2F%2Fwww.ietf.org%2Fmailma=
n%2Flistinfo%2Fart>


--_000_HE1PR07MB4441F094E5FAA479B3BCDA48934A9HE1PR07MB4441eurp_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
</head>
<body>
<div dir=3D"ltr">
<div></div>
<div>
<div dir=3D"ltr">Hi,</div>
<div dir=3D"ltr"><br>
</div>
<div dir=3D"ltr">Happy New Year!</div>
<div dir=3D"ltr"><br>
</div>
<div dir=3D"ltr">I sent a reply on the ART list, informing that 3GPP refere=
nces 2817, and asking whether the upgrade mechanism in 7230 is backward com=
patible with the one in 2817, and asking what/if will happen with the IANA =
registry upgrade value that 2817 defines.</div>
<div dir=3D"ltr"><br>
</div>
<div dir=3D"ltr">Regards,</div>
<div dir=3D"ltr"><br>
</div>
<div dir=3D"ltr">Christer</div>
<div id=3D"ms-outlook-mobile-signature" dir=3D"ltr">
<div dir=3D"ltr"><br>
</div>
</div>
</div>
<div id=3D"id-6afcc6bd-f98b-468b-ad62-b6582aad4d37" class=3D"ms-outlook-mob=
ile-reference-message">
<hr style=3D"display: inline-block; width: 98%; font-family: -webkit-standa=
rd; font-size: 12pt; color: rgb(0, 0, 0);" tabindex=3D"-1">
<div id=3D"divRplyFwdMsg" dir=3D"ltr"><font face=3D"Calibri, sans-serif"><b=
>From:</b> sipcore &lt;sipcore-bounces@ietf.org&gt; on behalf of Olle E. Jo=
hansson &lt;oej@edvina.net&gt;<br>
<b>Sent:</b> Monday, January 3, 2022 10:39 AM<br>
<b>To:</b> sipcore@ietf.org<br>
<b>Cc:</b> Mark Nottingham<br>
<b>Subject:</b> [sipcore] Fwd: [art] RFC2817, IPP, and XCAP
<div>&nbsp;</div>
</font></div>
Mark asked a question that relates to XCAP in the ART mailing list. Forward=
ing to SIPcore as I suspect there are many more people interested in XCAP o=
n this mailing list.
<div class=3D""><br class=3D"">
</div>
<div class=3D"">Happy new SIP year everyone!</div>
<div class=3D""><br class=3D"">
</div>
<div class=3D"">/O<br class=3D"">
<div><br class=3D"">
<blockquote type=3D"cite" class=3D"">
<div class=3D"">Begin forwarded message:</div>
<br class=3D"Apple-interchange-newline">
<div class=3D"" style=3D"margin-top:0px; margin-right:0px; margin-bottom:0p=
x; margin-left:0px">
<span class=3D"" style=3D"color:rgba(0,0,0,1.0)"><b class=3D"">From: </b></=
span><span class=3D"" style=3D"">Mark Nottingham &lt;<a href=3D"mailto:mnot=
@mnot.net" class=3D"">mnot@mnot.net</a>&gt;<br class=3D"">
</span></div>
<div class=3D"" style=3D"margin-top:0px; margin-right:0px; margin-bottom:0p=
x; margin-left:0px">
<span class=3D"" style=3D"color:rgba(0,0,0,1.0)"><b class=3D"">Subject: </b=
></span><span class=3D"" style=3D""><b class=3D"">[art] RFC2817, IPP, and X=
CAP</b><br class=3D"">
</span></div>
<div class=3D"" style=3D"margin-top:0px; margin-right:0px; margin-bottom:0p=
x; margin-left:0px">
<span class=3D"" style=3D"color:rgba(0,0,0,1.0)"><b class=3D"">Date: </b></=
span><span class=3D"" style=3D"">3 January 2022 at 07:24:42 CET<br class=3D=
"">
</span></div>
<div class=3D"" style=3D"margin-top:0px; margin-right:0px; margin-bottom:0p=
x; margin-left:0px">
<span class=3D"" style=3D"color:rgba(0,0,0,1.0)"><b class=3D"">To: </b></sp=
an><span class=3D"" style=3D""><a href=3D"mailto:art@ietf.org" class=3D"">a=
rt@ietf.org</a><br class=3D"">
</span></div>
<br class=3D"">
<div class=3D"">
<div class=3D"">Happy New Year, ART folks.<br class=3D"">
<br class=3D"">
I'm looking into whether we can move RFC2817 to Historic, because for HTTP'=
s purposes, the bits we actually use have moved into the Semantics document=
.<br class=3D"">
<br class=3D"">
However, I notice that RFC8010 still specifies the Upgrade mechanism for 'i=
pp' URLs. Can anyone from the IPP community speak as to whether that's actu=
ally in use?<br class=3D"">
<br class=3D"">
There's a similar question regarding RFC4825 and XCAP.<br class=3D"">
<br class=3D"">
If the damage caused by moving it to Historic would be too great, I might t=
ry to spin up a short applicability note that explained which bits moved in=
to semantics, and that what's left is only usable if a protocol using HTTP =
explicitly opts into it (like IPP).<br class=3D"">
<br class=3D"">
Cheers,<br class=3D"">
<br class=3D"">
<br class=3D"">
--<br class=3D"">
Mark Nottingham &nbsp;&nbsp;<a href=3D"https://protect2.fireeye.com/v1/url?=
k=3D31323334-501d5122-313273af-454445555731-2328097a3e27f5ac&amp;q=3D1&amp;=
e=3D23499f48-e28c-427d-a8a2-23beed6af6ca&amp;u=3Dhttps%3A%2F%2Fwww.mnot.net=
%2F" class=3D"">https://www.mnot.net/</a><br class=3D"">
<br class=3D"">
_______________________________________________<br class=3D"">
art mailing list<br class=3D"">
<a href=3D"mailto:art@ietf.org" class=3D"">art@ietf.org</a><br class=3D"">
<a href=3D"https://protect2.fireeye.com/v1/url?k=3D31323334-501d5122-313273=
af-454445555731-6d2584570e589803&amp;q=3D1&amp;e=3D23499f48-e28c-427d-a8a2-=
23beed6af6ca&amp;u=3Dhttps%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2Fart"=
>https://www.ietf.org/mailman/listinfo/art</a><br class=3D"">
</div>
</div>
</blockquote>
</div>
<br class=3D"">
</div>
</div>
</div>
</body>
</html>

--_000_HE1PR07MB4441F094E5FAA479B3BCDA48934A9HE1PR07MB4441eurp_--


From nobody Wed Jan 26 11:20:23 2022
Return-Path: <skhatri@qti.qualcomm.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 1EB8F3A1CD7; Wed, 26 Jan 2022 11:20:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=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 (1024-bit key) header.d=qti.qualcomm.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 p0f0GCS3tMz2; Wed, 26 Jan 2022 11:20:16 -0800 (PST)
Received: from esa.hc3962-90.iphmx.com (esa.hc3962-90.iphmx.com [216.71.140.77]) (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 B08F63A1CD3; Wed, 26 Jan 2022 11:20:16 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=qti.qualcomm.com; i=@qti.qualcomm.com; q=dns/txt; s=qccesdkim1; t=1643224816; x=1643829616; h=from:to:cc:subject:date:message-id:mime-version; bh=QWVtrxiCyCbgo8hbl8S2u8QMXDUAFxwsgXLCN1vp60Y=; b=eR8QNj46j8kt9N/inEazSXfDZ+yplYnx81TW5qGG7sIGir3kHaCtTZ1m i8GBekMzAIG5CJthene0pFFzd+o49E+A3sfYBSnGei8kHdJ64e+bg+n65 xlGYZu+UjJk+pFfuUBx3QXrhLMd6sKicWJm86rBuQy86vEL68MzeSoIHY A=;
Received: from mail-bn1nam07lp2048.outbound.protection.outlook.com (HELO NAM02-BN1-obe.outbound.protection.outlook.com) ([104.47.51.48]) by ob1.hc3962-90.iphmx.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 26 Jan 2022 19:20:15 +0000
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=Iz8anElb17eKUGnO5U6MPHUAXQ9oPK9ABxLR52n0+OQ+/B5jf7ACo77qcsNGeccK3M7p3EZ0o4luR9/REh9M5uBYVf1YBNGzWAdfB1/mZQgJfwvO5pCvLR//Cf/S14sNlOUE5IR7TaUwgt2gnTZY+36t5jeeSEu1ZghZsVi0o+Uz+PyaKWoKHlTktxk3W0K3fjIfID1/isLO9wos3G13DuZzadSnBoi7j7Xga7l/2xCzs0RC19i5S3pxlTy1cOkUQz+IVSBCUrNwlsq18ZQcFTaiuTQj/unz29tjW3e8cw+uFtXE3PEYRIk0A2P+/cEceUaouuDWoXXAIO4XXHClYg==
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-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=QWVtrxiCyCbgo8hbl8S2u8QMXDUAFxwsgXLCN1vp60Y=; b=h0PyKeZaBd/QMEMg7BAtp/E/BOdDV++CwrOwj4xWboAlr7lY9OONEf+Oq2TBfHybf0jZCwHrUiwBRqTiT0Rma1NRiTOs1x9WD/cwU0rxGcViLVpPN7Xyt90+2al6idLDSUnckft77LM9MFRvR8fcz5ZUbkRUsJyE6K34Kt2bc3n6dQ7eQCVl3ynCFur6YniA1hgUPQVekscQgQQP9VngJ3ODEg+CoKMd33kjC+6gUeN+s7i9PQgoQHbsOYXjySnxTf6jXSoWKTWJQ/NxQ33lS5kfmIpE7ecoip0SRkfP3XrjzUaxf3lGCFQNtYt0HjeZac656P6n6eA9Hubahv+uRw==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=none; dmarc=none; dkim=none; arc=none
Received: from SJ0PR02MB8733.namprd02.prod.outlook.com (2603:10b6:a03:3e0::12) by CH2PR02MB6021.namprd02.prod.outlook.com (2603:10b6:610:5::18) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.4888.11; Wed, 26 Jan 2022 19:20:13 +0000
Received: from SJ0PR02MB8733.namprd02.prod.outlook.com ([fe80::c836:acf8:bfb8:20d0]) by SJ0PR02MB8733.namprd02.prod.outlook.com ([fe80::c836:acf8:bfb8:20d0%4]) with mapi id 15.20.4909.017; Wed, 26 Jan 2022 19:20:13 +0000
From: Shrawan Khatri <skhatri@qti.qualcomm.com>
To: "sipcore@ietf.org" <sipcore@ietf.org>
CC: "sipcore-chairs@ietf.org" <sipcore-chairs@ietf.org>, Lena Chaponniere <lguellec@qti.qualcomm.com>, Waqar Zia <wzia@qti.qualcomm.com>
Thread-Topic: RFC draft status
Thread-Index: AdgS6YwWFYvqoVtiQ9yNstnkDEtgMA==
Date: Wed, 26 Jan 2022 19:20:12 +0000
Message-ID: <SJ0PR02MB873387A660A02CCE07172A5C8C209@SJ0PR02MB8733.namprd02.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: dkim=none (message not signed) header.d=none;dmarc=none action=none header.from=qti.qualcomm.com;
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 3eb379ad-b71c-4bd0-ca05-08d9e100e067
x-ms-traffictypediagnostic: CH2PR02MB6021:EE_
x-microsoft-antispam-prvs: <CH2PR02MB60210F5BA950418F89CA062E8C209@CH2PR02MB6021.namprd02.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:9508;
x-ms-exchange-senderadcheck: 1
x-ms-exchange-antispam-relay: 0
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: bGLN1QcOuZL7LBjzn0aK9kGp5m5pFNOOLKi+AenI/XKTYsGKA2pFwbpG9THavl5KJSNJXXjmEcurtPFDPxO3bBPRoO6E7DE1K/VT8XHNk/cOWKOTsGeWwsMgof5dgN9aKRC5oR+Fihild+hm/V1GjRh13n1O3gl3COgY7LmFFigW/ySjsLb6ohdSQDFlOVDMo6SAdlkTwyFaWzhGYN9Z+TnhXYexfZ1z5/MbzIQqKttAUaDFhkm0GpLR1I7tlDMJbzKdEoaS3GUK2ZmAPr6WtHaU2VpfcSMeQqcJnnm642Wiv863XNaQN21yfgXMprbY2CReEs/nzqP300+NA56dqIYUx3S7tgDmj/HLchbll6JWJbwPTy4aI3/COn1fSFE1y3QW24Q816qB4Bnc0rVsIoWhZBYBbbb47OhGmbMZEFslewkBHmlE6d4HZ7Lep466raif7z2XyxwCgC8OyhF+tcXjUq1Xmy1zzeszFUxobPIewgPLd4ldliGUTzZiNev1mCVVdFN+nRyFRMY/kwB7n5UJYvktSaHsgMQB5rpiridAnwVhC+N1Fgv/UOi3T0nKqZ+MKVlUJV+hTk6+Q+3w4t7l/xZHDIh8MS1FfyaGmC6iAFYjRFglBgNAxSHwMiV4O2iztdYJbWSRVt65p22D+k5LVa100xyKkRXC2+SoqMnlhBQpzZTa2WL2sHxrsd/tRMWaVjQ5C0Hki5cmj96cJf4dEjSpWyxEnNWk9uyYaTXraJAELqL85U5hjjSXS+OpL2r0KAV1suBzUFBTHhx0xV+RuRTYU5F+DhtELhQoGrc=
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:;  IPV:NLI; SFV:NSPM; H:SJ0PR02MB8733.namprd02.prod.outlook.com; PTR:; CAT:NONE;  SFS:(4636009)(366004)(450100002)(3480700007)(86362001)(83380400001)(26005)(9686003)(66556008)(6506007)(107886003)(7116003)(52536014)(186003)(2906002)(966005)(66446008)(64756008)(166002)(71200400001)(55016003)(66946007)(8936002)(76116006)(6916009)(4744005)(54906003)(66476007)(7696005)(33656002)(38100700002)(316002)(122000001)(5660300002)(4326008)(508600001)(38070700005)(8676002); DIR:OUT; SFP:1102; 
x-ms-exchange-antispam-messagedata-chunkcount: 1
x-ms-exchange-antispam-messagedata-0: =?us-ascii?Q?dR04D5Q4oFIDvw8LFsCAVsjQ5W7KLGy58HRMXWy7DENPYOE19bBt5Q75rG8D?= =?us-ascii?Q?HCzDj3u4mSEBb1D0C+KCIrRQ/H126aFU5kwhPKCWrMbP6mfKDTbPSh2k8XO+?= =?us-ascii?Q?U7zjcQcuaLPv6TbOsleu1DLhWTfevqNM/OmTAbCKa9bBReScwZTRFvRxtx5f?= =?us-ascii?Q?sEYDj3Qriasbpjo1J1v4D/2/Vkzo3Y9A3UsfLQ5tyOAtSUYTGZ1+pD9euPNC?= =?us-ascii?Q?WxxrsvQYwqy8hEQniCd5Nb74UnwFIHxWoD2C36wtntHXJP4QfkUmolUVfEb9?= =?us-ascii?Q?Dwb/ww/IGffRAppn1tYss2XVKhc+0m5bKfYHeSDB7JXB6r6iiqMljxI3i5pY?= =?us-ascii?Q?5a/a0i2wZSkAuxNGBcGpEVch3RM9fGUJOJ45m+D6iBbcwVGpKV53U7iNWLtc?= =?us-ascii?Q?MaB0XacHvBwDoM9daLwZN3lrCZCUY8BuBuoiMDseYlaf0gYT9B3aiCnWbjlL?= =?us-ascii?Q?rBkrsoZTTnjyInOn9FHEGAAEIFi1Pe3I7eSFuX7D9ATLGe8Jw719fbM1MaG5?= =?us-ascii?Q?7mQkX9SCQlg75xuXRQ0tc8IB5cgdTfvHzIEaR9qxD6lt1urS56Ew/FYLg2tP?= =?us-ascii?Q?oDHvrCQ6NfqiQgL0JGN4aLTxfApIqNBNxuNLheKJ/f7aJRBtgGf9M6cXEGi2?= =?us-ascii?Q?UE6W6FYjMBHBNk+OUtM+DTCGC3z2uXyrL/R/IxsJiFNEEkzEtS9C2wjgZMB6?= =?us-ascii?Q?x0qd5RMehGeb+Dy5WQ+eJUoO3N/APL33g3DE+SOvYIct6w83qle1/Vp4oeLy?= =?us-ascii?Q?ujxW5yon45zBb29rffy04QGLZ3MGFjRiaseJ3OsBj1UVS2UgVk9bd7TdSEFr?= =?us-ascii?Q?13iHy3Q+loGaZ78PWCix89ErtasKOWzwblAoDyeTYmNnmB31jLJqqoNwKuC0?= =?us-ascii?Q?mx7nGmFmDPFpAOT/Z/OMEPjdEA1lVbHHCWKep9HxCB52+7a1tWtiKRUZmk8i?= =?us-ascii?Q?zAaEdYjlf9VnUxlDbfVWIBWgWwo3Zx9M+U3ii3x1wmb0imMTYxituKqDi3jS?= =?us-ascii?Q?+aQv0Yd1fbefjDmm8iMDriHuVA4miOdcJ2Su/WJTFAprJjamuV4ZpYq4adyf?= =?us-ascii?Q?OKNEfuVMJc1fsm/Ege4xD1IOrMGQzl1gaARk2UPkPCUPvVovO3NlQBdyDT6r?= =?us-ascii?Q?KJdNafEEl/LsDOMddkWfsbFlVa+YzUHENx94U0iGiRlDFaxeHoGH4wsxii3x?= =?us-ascii?Q?8FNONaJagTg/4px3tr18KIHoPoaeXpJxUwLpiwroXdng0ESl5Ml5qLrwgpRP?= =?us-ascii?Q?DnZOsS1jQAI2eygRtIQlzC1dD19sMh6M5BAL0YEq0dENnNyMh+YM0HW9Ht16?= =?us-ascii?Q?HenAzxpuFduIWSQCg7p5WcYrHHALkJqU8hxzibqeg9hhKkywjuZJB8v4Y/jC?= =?us-ascii?Q?FFDHNCLyorhDIrQ3smHAh2mn8SfZOuZcfFCDB5bKwkyKnvfwTN2Bvgkg4zFe?= =?us-ascii?Q?sfNGvG0Rn9tJiicoJIvjnqFEgEjRNP4Iu93mjcXTkOJi/V0Ggyg0Akml6mu1?= =?us-ascii?Q?j81MQZq7PTuPnk/pQm6yasj1BjCYVQUu1rT6YvTTF8CJC1fFqfD1y5yfntov?= =?us-ascii?Q?FV1k9xuSMKvFYKz86TjcLxNCEz8gmhTnEtcoRrWcjIESUTrFYahooX23K7Ax?= =?us-ascii?Q?EMgvJPjamxU803NwnQfxcWRUEBaFZ0vKPwQko4uaBxIrtf5BdzY9zftsVDw3?= =?us-ascii?Q?vsAI2A=3D=3D?=
Content-Type: multipart/alternative; boundary="_000_SJ0PR02MB873387A660A02CCE07172A5C8C209SJ0PR02MB8733namp_"
MIME-Version: 1.0
X-OriginatorOrg: qti.qualcomm.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: SJ0PR02MB8733.namprd02.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 3eb379ad-b71c-4bd0-ca05-08d9e100e067
X-MS-Exchange-CrossTenant-originalarrivaltime: 26 Jan 2022 19:20:12.9846 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 98e9ba89-e1a1-4e38-9007-8bdabc25de1d
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: 3q6TZwJyEa0QVfnpMGC/XKYlPmV93xEz2vjVGDGGBDFsnRodYGnwI6USB7hsfPJ8669pD7r570WjPbjXGEpGKDcb6fUpMDM5DVWdFSQ1Qsk=
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CH2PR02MB6021
Archived-At: <https://mailarchive.ietf.org/arch/msg/sipcore/ZFWgrzNEMLPovBXz0oux_6bx7HE>
Subject: [sipcore] RFC draft status
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 Jan 2022 19:20:21 -0000

--_000_SJ0PR02MB873387A660A02CCE07172A5C8C209SJ0PR02MB8733namp_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Dear SIPCORE team,

We submitted the RFC Draft "A SIP Response Code(497) for Call Transfer Fail=
ure". The latest version (2) was submitted on January 24,2022 and it is goi=
ng to expire on July 2022. The Status of the RFC Draft is: I-D Exists - "Th=
e IESG has not started processing this draft, or has stopped processing it =
without publication".  Next step is

  *   Publication Requested
  *   AD is watching


The draft can be found in this link: https://datatracker.ietf.org/doc/draft=
-khatri-sipcore-call-transfer-fail-response/



This latest version addresses all comments received so far. We would be hap=
py to provide further input if the committee is waiting any. We would reall=
y appreciate if there are any further comments and if the draft could be co=
nsidered for adoption by the WG.



Thanking you



Sincerely,

Shrawan Khatri


--_000_SJ0PR02MB873387A660A02CCE07172A5C8C209SJ0PR02MB8733namp_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:x=3D"urn:schemas-microsoft-com:office:excel" xmlns:dt=3D"uuid:C2F4101=
0-65B3-11d1-A29F-00AA00C14882" xmlns:m=3D"http://schemas.microsoft.com/offi=
ce/2004/12/omml" xmlns=3D"http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:#0563C1;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri",sans-serif;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:435442518;
	mso-list-template-ids:-1982674224;}
@list l0:level1
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:"Courier New";
	mso-bidi-font-family:"Times New Roman";}
@list l0:level2
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:1.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:"Courier New";
	mso-bidi-font-family:"Times New Roman";}
@list l0:level3
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:1.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:"Courier New";
	mso-bidi-font-family:"Times New Roman";}
@list l0:level4
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:2.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:"Courier New";
	mso-bidi-font-family:"Times New Roman";}
@list l0:level5
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:2.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:"Courier New";
	mso-bidi-font-family:"Times New Roman";}
@list l0:level6
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:3.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:"Courier New";
	mso-bidi-font-family:"Times New Roman";}
@list l0:level7
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:3.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:"Courier New";
	mso-bidi-font-family:"Times New Roman";}
@list l0:level8
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:4.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:"Courier New";
	mso-bidi-font-family:"Times New Roman";}
@list l0:level9
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:4.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:"Courier New";
	mso-bidi-font-family:"Times New Roman";}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"#0563C1" vlink=3D"#954F72" style=3D"word-wrap:=
break-word">
<div class=3D"WordSection1">
<p style=3D"margin:0in">Dear SIPCORE team,<o:p></o:p></p>
<p style=3D"margin:0in">We submitted the RFC Draft &quot;A SIP Response Cod=
e(497) for Call Transfer Failure&quot;. The latest version (2) was submitte=
d on January 24,2022 and it is going to expire on July 2022. The Status of =
the RFC Draft is: I-D Exists - &quot;The IESG has
 not started processing this draft, or has stopped processing it without pu=
blication&quot;.&nbsp; Next step is
<o:p></o:p></p>
<ul style=3D"margin-top:0in" type=3D"circle">
<li class=3D"MsoNormal" style=3D"color:#222222;mso-list:l0 level1 lfo1;vert=
ical-align:middle">
<span style=3D"font-size:11.5pt;background:#F9F9F9">Publication Requested</=
span><o:p></o:p></li><li class=3D"MsoNormal" style=3D"color:#222222;mso-lis=
t:l0 level1 lfo1;vertical-align:middle">
<span style=3D"font-size:11.5pt;background:#F9F9F9">AD is watching</span><o=
:p></o:p></li></ul>
<p class=3D"MsoNormal" style=3D"margin-left:.5in;vertical-align:middle"><sp=
an style=3D"color:#222222"><o:p>&nbsp;</o:p></span></p>
<p style=3D"margin:0in">The draft can be found in this link: <a href=3D"htt=
ps://datatracker.ietf.org/doc/draft-khatri-sipcore-call-transfer-fail-respo=
nse/">
https://datatracker.ietf.org/doc/draft-khatri-sipcore-call-transfer-fail-re=
sponse/</a><o:p></o:p></p>
<p style=3D"margin:0in">&nbsp;<o:p></o:p></p>
<p style=3D"margin:0in">This latest version addresses all comments received=
 so far. We would be happy to provide further input if the committee is wai=
ting any. We would really appreciate if there are any further comments and =
if the draft could be considered for
 adoption by the WG.<o:p></o:p></p>
<p style=3D"margin:0in">&nbsp;<o:p></o:p></p>
<p style=3D"margin:0in">Thanking you<o:p></o:p></p>
<p style=3D"margin:0in">&nbsp;<o:p></o:p></p>
<p style=3D"margin:0in">Sincerely,<o:p></o:p></p>
<p style=3D"margin:0in">Shrawan Khatri<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</body>
</html>

--_000_SJ0PR02MB873387A660A02CCE07172A5C8C209SJ0PR02MB8733namp_--


From nobody Wed Jan 26 11:55:35 2022
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 DD2023A1DF7; Wed, 26 Jan 2022 11:55:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.848
X-Spam-Level: 
X-Spam-Status: No, score=-1.848 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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=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 ukHJCgB-sDM5; Wed, 26 Jan 2022 11:55:28 -0800 (PST)
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 9DA2E3A1DFA; Wed, 26 Jan 2022 11:55:28 -0800 (PST)
Received: by mail-ej1-x62b.google.com with SMTP id j2so899077ejk.6; Wed, 26 Jan 2022 11:55:28 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=WAcfIAYx8YefFBUy5cnnrHDKuuvrQ1iJgGSV/dj3Y7M=; b=RTfpSzN57vWUKkCR+1/Vh8NNm83YVR5LZM+iP+62tKGAC3Wbo4ZAtX8rEQGrflYsnw BBoluwsdsFohVh+xTpl7BNTKuY6Yw5AiomiOTdgui9LxL8sGfIBJRQI/pIR3fxmIQ99L Hc7sMxr2H6pbRMfWvViUiVl7ZPoL+cWetoS6gM4kCc6WSAP54PYS72YP5Q5LcW0futfr 7ZxDl3GIk7nN3jgDrJt6ucAqAPRGF8W6Hnk6xKdS0bS/Mh5iwcszQtn7nBQj94How5l9 MRddzoiJW0vVPjCR9koXatlZfL9d2p1bQj9As/9tIJ1mgCFZaCK/FAqeJkWL0yeikJ8T /W/A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=WAcfIAYx8YefFBUy5cnnrHDKuuvrQ1iJgGSV/dj3Y7M=; b=3x1Bbecw80lxQLQxKTXJ6lz6SetNI+5k1wXzJwYYC3SOpjkshU9I2p6gnTvDkcQyX+ BPyhYhKoVwLJ5H4s5aHU/G2OxaeoS1o3+iVlTW0VsEHR89XS1urD6NXARdld35/A9kRL HNg0wS+X3QoL+VND4WEeDMHmXjCM43wQqsom1huPyjjUY5UDVayXKcKdb+6wPvg1mJOz AXjBAsYot9Eta5GKgMX26I8DmOzRJ2TdYM59S0c1+5+NIOl2zZTpfZhP12Hd6qi5hC4w U/QZaahrKvaOdeXeZ/15DcOcw01ZFO/FeFbQhXi3sr7Uo6dLPqHBmcYFbxCY1nekyYMm eUmg==
X-Gm-Message-State: AOAM532HWbLRo2CWOxO65X1mcVCbcHx/C1H3dLKNPRGJqCbI/8pZIdhX XKzD2TpJxh0lb6BEQW9wurkpOb7O1bt3ScHCK7oNcEVc
X-Google-Smtp-Source: ABdhPJyUZuhoYR4MWbyhTg7qyUA3AoYBELaTr7N85jnWRa/UDbk9DpMuK0fLOyhVWfvUUVuDvjeoRZIa0Ug8SKxeRy0=
X-Received: by 2002:a17:907:7f8c:: with SMTP id qk12mr268425ejc.758.1643226925752;  Wed, 26 Jan 2022 11:55:25 -0800 (PST)
MIME-Version: 1.0
References: <SJ0PR02MB873387A660A02CCE07172A5C8C209@SJ0PR02MB8733.namprd02.prod.outlook.com>
In-Reply-To: <SJ0PR02MB873387A660A02CCE07172A5C8C209@SJ0PR02MB8733.namprd02.prod.outlook.com>
From: Ranjit Avasarala <ranjitkav12@gmail.com>
Date: Wed, 26 Jan 2022 13:55:14 -0600
Message-ID: <CAFXT-psBQYQhROPQ82aLSb6_m-MuZS+vBsoQYQcm_ODqmbCjkQ@mail.gmail.com>
To: Shrawan Khatri <skhatri@qti.qualcomm.com>
Cc: "sipcore@ietf.org" <sipcore@ietf.org>, Waqar Zia <wzia@qti.qualcomm.com>,  Lena Chaponniere <lguellec@qti.qualcomm.com>,  "sipcore-chairs@ietf.org" <sipcore-chairs@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000031e33405d6819523"
Archived-At: <https://mailarchive.ietf.org/arch/msg/sipcore/wNw57iWZ6XeSAp6gQeP4OfMz2YM>
Subject: Re: [sipcore] RFC draft status
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 Jan 2022 19:55:33 -0000

--00000000000031e33405d6819523
Content-Type: text/plain; charset="UTF-8"

Hi Shrawan

Though I agree that you may need a response code for indicating call
transfer failure, the issue is - server is unable to do the transfer i.e.
refusing or cannot transfer, then I think a 5xx would be more appropriate
as it is server issue. So a 500 Internal Server Error with Reason:  Call
Transfer Refused would be more appropriate

Thoughts?


On Wed, Jan 26, 2022 at 1:20 PM Shrawan Khatri <skhatri@qti.qualcomm.com>
wrote:

> Dear SIPCORE team,
>
> We submitted the RFC Draft "A SIP Response Code(497) for Call Transfer
> Failure". The latest version (2) was submitted on January 24,2022 and it is
> going to expire on July 2022. The Status of the RFC Draft is: I-D Exists -
> "The IESG has not started processing this draft, or has stopped processing
> it without publication".  Next step is
>
>    - Publication Requested
>    - AD is watching
>
>
>
> The draft can be found in this link:
> https://datatracker.ietf.org/doc/draft-khatri-sipcore-call-transfer-fail-response/
>
>
>
> This latest version addresses all comments received so far. We would be
> happy to provide further input if the committee is waiting any. We would
> really appreciate if there are any further comments and if the draft could
> be considered for adoption by the WG.
>
>
>
> Thanking you
>
>
>
> Sincerely,
>
> Shrawan Khatri
>
>
> _______________________________________________
> sipcore mailing list
> sipcore@ietf.org
> https://www.ietf.org/mailman/listinfo/sipcore
>

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

<div dir=3D"ltr">Hi Shrawan<div><br></div><div>Though I agree that you may =
need a response code for indicating call transfer failure, the issue is - s=
erver is unable to do the transfer i.e. refusing or cannot transfer, then I=
 think a 5xx would be more appropriate as it is server issue. So a 500 Inte=
rnal Server Error with Reason:=C2=A0 Call Transfer Refused would be more ap=
propriate</div><div><br></div><div>Thoughts?</div><div><br></div></div><br>=
<div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Wed, Ja=
n 26, 2022 at 1:20 PM Shrawan Khatri &lt;<a href=3D"mailto:skhatri@qti.qual=
comm.com">skhatri@qti.qualcomm.com</a>&gt; wrote:<br></div><blockquote clas=
s=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid r=
gb(204,204,204);padding-left:1ex">





<div lang=3D"EN-US" style=3D"overflow-wrap: break-word;">
<div class=3D"gmail-m_-1660840468603322513WordSection1">
<p style=3D"margin:0in">Dear SIPCORE team,<u></u><u></u></p>
<p style=3D"margin:0in">We submitted the RFC Draft &quot;A SIP Response Cod=
e(497) for Call Transfer Failure&quot;. The latest version (2) was submitte=
d on January 24,2022 and it is going to expire on July 2022. The Status of =
the RFC Draft is: I-D Exists - &quot;The IESG has
 not started processing this draft, or has stopped processing it without pu=
blication&quot;.=C2=A0 Next step is
<u></u><u></u></p>
<ul style=3D"margin-top:0in" type=3D"circle">
<li class=3D"MsoNormal" style=3D"color:rgb(34,34,34);vertical-align:middle"=
>
<span style=3D"font-size:11.5pt;background:rgb(249,249,249)">Publication Re=
quested</span><u></u><u></u></li><li class=3D"MsoNormal" style=3D"color:rgb=
(34,34,34);vertical-align:middle">
<span style=3D"font-size:11.5pt;background:rgb(249,249,249)">AD is watching=
</span><u></u><u></u></li></ul>
<p class=3D"MsoNormal" style=3D"margin-left:0.5in;vertical-align:middle"><s=
pan style=3D"color:rgb(34,34,34)"><u></u>=C2=A0<u></u></span></p>
<p style=3D"margin:0in">The draft can be found in this link: <a href=3D"htt=
ps://datatracker.ietf.org/doc/draft-khatri-sipcore-call-transfer-fail-respo=
nse/" target=3D"_blank">
https://datatracker.ietf.org/doc/draft-khatri-sipcore-call-transfer-fail-re=
sponse/</a><u></u><u></u></p>
<p style=3D"margin:0in">=C2=A0<u></u><u></u></p>
<p style=3D"margin:0in">This latest version addresses all comments received=
 so far. We would be happy to provide further input if the committee is wai=
ting any. We would really appreciate if there are any further comments and =
if the draft could be considered for
 adoption by the WG.<u></u><u></u></p>
<p style=3D"margin:0in">=C2=A0<u></u><u></u></p>
<p style=3D"margin:0in">Thanking you<u></u><u></u></p>
<p style=3D"margin:0in">=C2=A0<u></u><u></u></p>
<p style=3D"margin:0in">Sincerely,<u></u><u></u></p>
<p style=3D"margin:0in">Shrawan Khatri<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</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>

--00000000000031e33405d6819523--


From nobody Thu Jan 27 10:04:31 2022
Return-Path: <internet-drafts@ietf.org>
X-Original-To: sipcore@ietf.org
Delivered-To: sipcore@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id BEE723A0830; Thu, 27 Jan 2022 10:04:18 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
Cc: sipcore@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 7.43.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: sipcore@ietf.org
Message-ID: <164330665864.9156.13772461448490497492@ietfa.amsl.com>
Date: Thu, 27 Jan 2022 10:04:18 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/sipcore/nxZ1dzEVh91AdA0R27XZlrJEWFg>
Subject: [sipcore] I-D Action: draft-ietf-sipcore-rfc4028bis-06.txt
X-BeenThere: sipcore@ietf.org
X-Mailman-Version: 2.1.29
List-Id: SIP Core Working Group  <sipcore.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sipcore>, <mailto:sipcore-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sipcore/>
List-Post: <mailto:sipcore@ietf.org>
List-Help: <mailto:sipcore-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sipcore>, <mailto:sipcore-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 27 Jan 2022 18:04:19 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Session Initiation Protocol Core WG of the IETF.

        Title           : Session Timers in the Session Initiation Protocol (SIP)
        Authors         : Christer Holmberg
                          Steve Donovan
                          Jonathan Rosenberg
	Filename        : draft-ietf-sipcore-rfc4028bis-06.txt
	Pages           : 26
	Date            : 2022-01-27

Abstract:
   This document defines an extension to the Session Initiation Protocol
   (SIP).  This extension allows for a periodic refresh of SIP sessions
   through a re-INVITE or UPDATE request.  The refresh allows both user
   agents and proxies to determine whether the SIP session is still
   active.  The extension defines two new header fields: Session-
   Expires, which conveys the lifetime of the session, and Min-SE, which
   conveys the minimum allowed value for the session timer.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-sipcore-rfc4028bis/

There is also an htmlized version available at:
https://datatracker.ietf.org/doc/html/draft-ietf-sipcore-rfc4028bis-06

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-sipcore-rfc4028bis-06


Internet-Drafts are also available by rsync at rsync.ietf.org::internet-drafts


