IETF Logo Mail Archive

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

Eric Rescorla <ekr@rtfm.com> Mon, 07 January 2019 22:08 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 EA88E12E04D for <sipcore@ietfa.amsl.com>; Mon, 7 Jan 2019 14:08:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, 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 R7YtdD0FICI1 for <sipcore@ietfa.amsl.com>; Mon, 7 Jan 2019 14:08:24 -0800 (PST)
Received: from mail-lf1-x12b.google.com (mail-lf1-x12b.google.com [IPv6:2a00:1450:4864:20::12b]) (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 CB4A512E036 for <sipcore@ietf.org>; Mon, 7 Jan 2019 14:08:23 -0800 (PST)
Received: by mail-lf1-x12b.google.com with SMTP id p6so1491797lfc.1 for <sipcore@ietf.org>; Mon, 07 Jan 2019 14:08:23 -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=msBT2HY6aQ3I6oFR5WQOrFi3paE84NhrLitLQEcfCGA=; b=fYD9pgLDotua/+w1uf8WiExOZ0uLJ1BQ4iDaWteQ3Ri942Dzk+zVNGhUcrX6ogRt0A sJIUow2nvahJxp7z/GIFWECuHhOB6pui7xENevBlJx2YKqt7COR7+Mtx0QHs/RszkBE7 fFU1JJuh2W+ZOTo8+UyE05NfTC/kd52Re9Hs4103/PF/faSbDQlrQkBzLXtJoxdi++Az xKUwBUhFeeeYkiPZCydGi33Gwy11zU6WTFwP5YVrSKJpZuQRQoyGNjmX+WSr+cvweGBj sfAv4yKzIqYTTkfGwou1DQWhjgkrkdIV90zeKP3qH9l048vGsjdtf8mZAKjUoJErPThR 7MuQ==
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=msBT2HY6aQ3I6oFR5WQOrFi3paE84NhrLitLQEcfCGA=; b=cXNz/3TMufIAKud9+KdRQ3ks3buxzOqZohhfOVPPLhZWwJalqq8tI08DUxyp3mRp9y EvW/wq1BMRASrq8+zoKLBmFuil1nGR2AgDa/UFjLB7/Lu0GR8CQV78CAMhYRMRFI5in0 H/qeFxl9DNaBfN4WQY/L+HxX+ujIixFaTf9Ov4GQlht1mCVsIPhmsNA2l966sF05S6eh A+PeYidghZZwJYcPFbZj+6HyJ+rBB0yXOebUP9qkAGpoVRfhotH8ZFgCszfpSvNqKPY1 V/NAYdgbomteafTXY0YxfreXE3zjsJKStgP05wZp6r2d10f/Ff9SgctgFvdpactnQHMz uiHg==
X-Gm-Message-State: AA+aEWayvM+k2eTnM9ZxlfTA4QCmAp4d6WpBR1XY7jzMBx+0paCA9hoK 94VaisCDEIGvIR0uKJTWBFtSBYvWhTWamGXftDw/tg==
X-Google-Smtp-Source: AFSGD/XdeOu3/QlFuJ5/7NkCf7wcxzoemQRXkabxKn7WlUwctJRnopWpqO42AqsG6MrHZpaJ+GX4Oh8MLLh3p3tfZxE=
X-Received: by 2002:a19:ca51:: with SMTP id h17mr29489169lfj.126.1546898901914; Mon, 07 Jan 2019 14:08:21 -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> <HE1PR07MB31611682A1DA90ADBC1E620D93890@HE1PR07MB3161.eurprd07.prod.outlook.com>
In-Reply-To: <HE1PR07MB31611682A1DA90ADBC1E620D93890@HE1PR07MB3161.eurprd07.prod.outlook.com>
From: Eric Rescorla <ekr@rtfm.com>
Date: Mon, 07 Jan 2019 14:07:43 -0800
Message-ID: <CABcZeBNC-3Gc3LStnRwn2T_SSeO6Zo=S3Oy+90MX1xjxo0njgA@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="0000000000008d6cca057ee577de"
Archived-At: <https://mailarchive.ietf.org/arch/msg/sipcore/PFrdETSwu4ar7VfQ35bjof5s3qA>
Subject: Re: [sipcore] Eric Rescorla's Discuss on draft-ietf-sipcore-sip-push-21: (with DISCUSS and COMMENT) - the COMMENT issues - part 3
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, 07 Jan 2019 22:08:26 -0000

On Mon, Jan 7, 2019 at 11:47 AM Christer Holmberg <
christer.holmberg@ericsson.com> wrote:

> Seems like I skipped one issue in my previous reply.
>
>
> S 5.3.2.
> >>
> >>      If the proxy has knowledge that the UA is awake, and that the UA is
> >>      able to receive the SIP request without first sending a REGISTER
> >>      request, the proxy MAY choose to not request a push notification
> >>      towards the UA (and wait for the associated REGISTER request and
> 2xx
> >>      response) before it tries to forward the SIP request towards the
> UA.
> >
> >Why not race these?
>
> One could do that, but I don't think it should be mandated.
>
>
> >The current text prohibits racing if you *don't* know that the UA is
> awake.
>
> The basic assumption of the mechanism is that a UA cannot receive SIP
> requests before it has received the push notification, sent the REGISTER
> etc.
>

But that may or may not be true, depending on whether the device has gone
to sleep

-Ekr


> Regards,
>
> Christer
>
>
>
>

v2.23.0 | Report a Bug | By Email