Re: [sipcore] Eric Rescorla's Discuss on draft-ietf-sipcore-sip-push-21: (with DISCUSS and COMMENT) - the COMMENT issues - part 2 - section 4_1

Eric Rescorla <ekr@rtfm.com> Fri, 11 January 2019 22:06 UTC

Return-Path: <ekr@rtfm.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 91601128CE4 for <sipcore@ietfa.amsl.com>; Fri, 11 Jan 2019 14:06:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.041
X-Spam-Level:
X-Spam-Status: No, score=-2.041 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.142, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=rtfm-com.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 7c6IgNlYKwc0 for <sipcore@ietfa.amsl.com>; Fri, 11 Jan 2019 14:06:53 -0800 (PST)
Received: from mail-lf1-x130.google.com (mail-lf1-x130.google.com [IPv6:2a00:1450:4864:20::130]) (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 CFAA81200D7 for <sipcore@ietf.org>; Fri, 11 Jan 2019 14:06:52 -0800 (PST)
Received: by mail-lf1-x130.google.com with SMTP id a8so11871077lfk.5 for <sipcore@ietf.org>; Fri, 11 Jan 2019 14:06:52 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rtfm-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=/sbquMt9lpzvlYQs/kvi0Zrjysz7mJXTNi6/eNVBNvk=; b=DvmnEEmllgPF9W4WyNAJ0jHnRzExmRbKH8K8V8BMFHtd+nwh+kC8aJacVIWr5VUBYv wx+pV19/PnK2urPMxpFwuiFFJBLajicztl7ffF+m2tKOtc9d6YLBUhLw2gssO+69S529 SI/ksFITVkjcqHBAjyFDAnJOz2ahitjWLpsFjXaXqhtAK5N4kQ4xlTLNlINyJ1grG77T s7a2M/fw5ZX5XZxqkdEv4nPjXjKv3SYPN1XzncRDrF29cLnBwf3TDZ19wBj6a3all4VX etGJqFJnDQ0dmGY0DK/zb2AfE+GJnLWSYfKjgKdnDYysoqjRqrAeMRSKs+97BwJPPaBD CUKQ==
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=/sbquMt9lpzvlYQs/kvi0Zrjysz7mJXTNi6/eNVBNvk=; b=Yxf0v6SqjkyqIhdBF843OLYclabsKFQIsn6WyICm+TlQhxUjhasHFbCIwYkgB29Z7n vp7sog5QG259aWVoNQfHTfrbXHxHQBKvPk7fSnBy5v7OiWVDWdGLbxEwZayMOWbpAizP +3GK8ac8yIYImAgoD33UJizRCag3cbZAJoQARaTtyLGL8Wt3c7ffUUjVS1HadcXe98Tl +GI+mQelLCDz/SJTzdRVeBGm3xP1giFTYg6GPC2nt185p5PeAnDf5DYCldVJZI0zeG/V vJ7aizGijzCoWpKO6jGJSXYgPZOnu2YCAlG+NfmdTGz6N2R339BcffjwaVPDKH0g1Qxl 5bwg==
X-Gm-Message-State: AJcUukcNOnODdfPSdmH6v7bQC5xuWvtzqOiUn0GHLOKnq3lfIEaCmdDY 3mUNqZFbRcEoh1wqKIEHH+4b5Ft3HjipwjxIPLikR+Q07I4=
X-Google-Smtp-Source: ALg8bN6B1AsSmeX5+TdGuT7kyG1h/HSj5jaE6/i5yZQ3eZcgoDRZxLn6TdZRHzMfR23z6hS+fDQmGrySbxGI30UUe9c=
X-Received: by 2002:a19:a9d2:: with SMTP id s201mr8684628lfe.154.1547244411025; Fri, 11 Jan 2019 14:06:51 -0800 (PST)
MIME-Version: 1.0
References: <154681733718.17024.3190954246737206843.idtracker@ietfa.amsl.com> <HE1PR07MB31611EECBA89EF1FC46D756C93890@HE1PR07MB3161.eurprd07.prod.outlook.com> <CABcZeBM-SdQH4_92uo5-KWWG=Wnb+1u=j7u-1J3FzjjymQYJhA@mail.gmail.com> <HE1PR07MB3161A0F37182BC9AEF1BB4DC93890@HE1PR07MB3161.eurprd07.prod.outlook.com> <HE1PR07MB3161793A1009C6D771F0417393850@HE1PR07MB3161.eurprd07.prod.outlook.com>
In-Reply-To: <HE1PR07MB3161793A1009C6D771F0417393850@HE1PR07MB3161.eurprd07.prod.outlook.com>
From: Eric Rescorla <ekr@rtfm.com>
Date: Fri, 11 Jan 2019 14:06:12 -0800
Message-ID: <CABcZeBP=eWxvyQgrvHr8VY7BJW54FyeRHZcPcfPu1QGQkQ=zPw@mail.gmail.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
Cc: The IESG <iesg@ietf.org>, "br@brianrosen.net" <br@brianrosen.net>, "sipcore@ietf.org" <sipcore@ietf.org>, "draft-ietf-sipcore-sip-push@ietf.org" <draft-ietf-sipcore-sip-push@ietf.org>, "sipcore-chairs@ietf.org" <sipcore-chairs@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000008012d6057f35e9b8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/sipcore/I5j_OXIDELm0A3q2HbUENkUtnyM>
Subject: Re: [sipcore] Eric Rescorla's Discuss on draft-ietf-sipcore-sip-push-21: (with DISCUSS and COMMENT) - the COMMENT issues - part 2 - section 4_1
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, 11 Jan 2019 22:06:54 -0000

On Fri, Jan 11, 2019 at 1:54 PM Christer Holmberg <
christer.holmberg@ericsson.com> wrote:

> Hi,
>
>
> S 4.1.
> >>>      capability indicator, the UA SHOULD only send a re-registration
> >>>      REGISTER request when it receives a push notification (even if
> the UA
> >>>      is able to use a non-push mechanism for sending re-registration
> >>>      REGISTER requests), or when there are circumstances (e.g., if the
> UA
> >>>      is assigned new contact parameters due to a network configuration
> >>>      change) that require an immediate REGISTER request to be sent.
> >>
> >>This text doesn't seem correct. If the initial response doesn't
> >>contain "sip.pns" then you probably would still want to send regular
> >>REGISTERs
>
> If the response doesn't contain "sip.pns" then none of the procedures
> apply.
>

As before, the writing in the document makes it very hard to determine this.

-Ekr


> Earlier in the section the text says:
>
>   "In other cases, the UA MUST NOT assume that the proxy will request that
> push notifications is
>    sent to the UA,   and the actions taken by the UA might be dependent on
> implementation or
>    deployment architecture, and are outside the scope of this document."
>
> So, if the UA wants to fallback to "regular" mode it can do so, but it is
> outside the scope of the document.
>
> Regards,
>
> Christer
>