IETF Logo Mail Archive

Re: [sipcore] I-D Action: draft-sparks-sipcore-refer-explicit-subscription-00.txt

Brett Tate <brett@broadsoft.com> Tue, 07 October 2014 10:29 UTC

Return-Path: <brett@broadsoft.com>
X-Original-To: sipcore@ietfa.amsl.com
Delivered-To: sipcore@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D383E1A1B7D for <sipcore@ietfa.amsl.com>; Tue, 7 Oct 2014 03:29:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.779
X-Spam-Level:
X-Spam-Status: No, score=-0.779 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, J_CHICKENPOX_51=0.6, J_CHICKENPOX_71=0.6, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=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 v5OUS2k12l5h for <sipcore@ietfa.amsl.com>; Tue, 7 Oct 2014 03:29:38 -0700 (PDT)
Received: from mail-qg0-f46.google.com (mail-qg0-f46.google.com [209.85.192.46]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D9D071A1B25 for <sipcore@ietf.org>; Tue, 7 Oct 2014 03:29:37 -0700 (PDT)
Received: by mail-qg0-f46.google.com with SMTP id z60so4935014qgd.5 for <sipcore@ietf.org>; Tue, 07 Oct 2014 03:29:37 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:references:in-reply-to:mime-version :thread-index:date:message-id:subject:to:content-type; bh=Nju6WEl9NJL8zotnSyAG3ZEZGK9fcE88z6e80LxkCtQ=; b=fPfYSVtzCm8E6vw31494Sw5Osdmbbr9T0EOdt+xDAcU3la9MDWJntvAwwsPEmcu2te k2mTCPYUPzOlH1WH17rtNOxT0/GdjmkOjHFGQF9cIQM0UeIyU2/3Hs7rz26UYvHKYnhs 6GH8UJqthYZun7dEq/rZwVS2LLljwRYLlZSDazjUVi3qBilSugaa614w9mmTXVyTrs8U ajPsm60lKqs7KGpl5u896O5aax4LfSb+D7yW+GXVvtgwp2qCFTnrcqDy4XWoupeBJa2u z8+xMFrLr2ZiwPwTJWGl1Y6DhDrbcpGME2Iadtc8s6EQZk+OIu/r+kovyfykjNVTPG6b p97Q==
X-Gm-Message-State: ALoCoQl8GM3qRE78f9UwY4xUGbHKCTdwxILgc2LV8VcZKmt8eZEsogUvQyBV+i63Vm5U7dPYJ6gv
X-Received: by 10.140.19.142 with SMTP id 14mr34661701qgh.28.1412677776965; Tue, 07 Oct 2014 03:29:36 -0700 (PDT)
From: Brett Tate <brett@broadsoft.com>
References: <78CFBBA55ECDC0ietf.shinji@gmail.com> <53F39858.9000106@alum.mit.edu> <FFCFBC226B9DC1ietf.shinji@gmail.com> <09e19e6cf16416d0d7db7d969cde5fde@mail.gmail.com> <7ECFE1D6928D51ietf.shinji@gmail.com>
In-Reply-To: <7ECFE1D6928D51ietf.shinji@gmail.com>
MIME-Version: 1.0
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQKJFczc/sUgi56rfylPNQKUV9gkdwJ7RhT4AeyQ2igB0tIoUAK3X9THmmpwc6A=
Date: Tue, 07 Oct 2014 06:29:36 -0400
Message-ID: <7842a70266cc3d3aa5bf3da6360e6a11@mail.gmail.com>
To: OKUMURA Shinji <ietf.shinji@gmail.com>, sipcore@ietf.org
Content-Type: text/plain; charset="UTF-8"
Archived-At: http://mailarchive.ietf.org/arch/msg/sipcore/TBHSvENtYEIr7lXOE2C5d1Rh8DA
Subject: Re: [sipcore] I-D Action: draft-sparks-sipcore-refer-explicit-subscription-00.txt
X-BeenThere: sipcore@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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, 07 Oct 2014 10:29:39 -0000

>     subscriber                              notifier
>         |                                       |
>         |   SUBSCRIBE in dialog                 |
>         |-------------------------------------->| dialog1
>         |   callid:1, fromtag:a, totag:b        |
>         |                                       |
>         |   200 OK(SUBSCRIBE)                   |
>         |<--------------------------------------| dialog1
>         |                                       |
>         |   NOTIFY                              |
>         |<--------------------------------------| dialog2
>         |   callid:1, fromtag:c, totag:a        |
>         |                                       |
>
> This NOTIFY seems to satisfy the RFC 6665 restriction(section 4.4.1).
> Does this NOTIFY act against accepted wisdom for SIP?

RFC 6665 section 4.2.1.2:

"Upon successfully accepting or refreshing a subscription, notifiers
  MUST send a NOTIFY request immediately to communicate the current
  resource state to the subscriber.  This NOTIFY request is sent on the
  same dialog as created by the SUBSCRIBE response."

RFC 6665 section 4.4.3:

"Upon receipt of this SUBSCRIBE request, the notifier (or notifiers,
  if the SUBSCRIBE request was forked) will send a NOTIFY request
  containing resource state in the same dialog."

v2.23.0 | Report a Bug | By Email