Re: [sipcore] Draft new: draft-mohali-sipcore-originating-cdiv-parameter-00
Ranjit Avasarala <ranjitkav0811@gmail.com> Tue, 04 April 2017 15:27 UTC
Return-Path: <ranjitkav0811@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 67E4F1296CC for <sipcore@ietfa.amsl.com>; Tue, 4 Apr 2017 08:27:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.748
X-Spam-Level:
X-Spam-Status: No, score=-1.748 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 zCe6NWA5z19Z for <sipcore@ietfa.amsl.com>; Tue, 4 Apr 2017 08:27:42 -0700 (PDT)
Received: from mail-pg0-x229.google.com (mail-pg0-x229.google.com [IPv6:2607:f8b0:400e:c05::229]) (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 5F3B11296C6 for <sipcore@ietf.org>; Tue, 4 Apr 2017 08:27:42 -0700 (PDT)
Received: by mail-pg0-x229.google.com with SMTP id g2so153657169pge.3 for <sipcore@ietf.org>; Tue, 04 Apr 2017 08:27:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=SSaTcWtmy+8ZKQPC0yoI+2lYKNmb6MaqxqCDnC/5Qx8=; b=pDhfJWiHCaljEWr48oO/B+dei9Mj8X2meUuAiQ1SQV4YmN8ZFvQZN3eE4gMHuGB4jG tWjh65uXDk6o3friERWSORJZN6zN7ppzM3EOsNbtDnvBjL1kr2ch8HuzIBD37aTEXwR2 OCi9p3iYIYz1rdlW85AAWHUCy+EatJVLJSbP/JUm82Qol1dattQlazoq2yfdsYaViHbS QWzzWL0fXV3eDEL5XrRJwWkJXD2DOwaBOA63//rZ5mOzzesLuCOPGsmZH8MEbSDdPwt/ r/VnoTkmqhmeuo+w9cMhvPOaKHoVZKs14P62FSJXZ20Kf+3drq31XPTKaSt32jSfIYiP iouQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=SSaTcWtmy+8ZKQPC0yoI+2lYKNmb6MaqxqCDnC/5Qx8=; b=eb1HRLiiituPPOihSvlyeseVoPs81Ab//8H1bGHBNE/qfRdSZ92Ch1TXozYDJWTGvO xFlSe9rjysBBw6g/ixwWJx/HD5wCKUOYILUlp/DLGIk2m6vKjjEngcelwzCcpKCOuPTb RSWOOqs+CbQj4QDH+F1HzXJHKVyNcPEh7KjpNc1Gl16jSHdpn0Gs/4DRG/dPDlfLzZVf TeP+q6lQxrsqJ+xJYO1P/j+aeAu3EmAreLJw1/cn/bCrkk9oTb+mUeV+rxkTKgCAC3D/ 1aVDiJOMu4K8AcrvrF/MkR5TrMd7b/OwRmPF4tmyby8H3uAVaoRP5O7N0JT+MHKIq5W5 XzTQ==
X-Gm-Message-State: AFeK/H2E774WGm8G8urVqAAToRQP7jwOjdohwQCtFeVKNTDn2YB/fLP4K+22B5UOjEQfGUgZGKnrSYF1ILD7Mw==
X-Received: by 10.99.42.78 with SMTP id q75mr24592281pgq.144.1491319662013; Tue, 04 Apr 2017 08:27:42 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.100.154.239 with HTTP; Tue, 4 Apr 2017 08:27:41 -0700 (PDT)
In-Reply-To: <f7467708296648d6a8877e9b3956de53@HE105828.emea1.cds.t-internal.com>
References: <25855_1489353730_58C5BC02_25855_10494_1_8B970F90C584EA4E97D5BAAC9172DBB81C935BDC@OPEXCLILMA4.corporate.adroot.infra.ftgroup> <58b9213c-1fb1-95f7-6888-60f7a754fc4f@nostrum.com> <f7467708296648d6a8877e9b3956de53@HE105828.emea1.cds.t-internal.com>
From: Ranjit Avasarala <ranjitkav0811@gmail.com>
Date: Tue, 04 Apr 2017 10:27:41 -0500
Message-ID: <CA+CMEWd3+dd+m8DjUyyiCm_Xe+9S3E2+jhPN7+z0UwcbSfjzgw@mail.gmail.com>
To: R.Jesske@telekom.de
Cc: mahoney@nostrum.com, SIPCORE <sipcore@ietf.org>
Content-Type: multipart/alternative; boundary="001a114693dab37371054c58ea0a"
Archived-At: <https://mailarchive.ietf.org/arch/msg/sipcore/ohoO8CFTK94CktHj6hIWyklWBRo>
Subject: Re: [sipcore] Draft new: draft-mohali-sipcore-originating-cdiv-parameter-00
X-BeenThere: sipcore@ietf.org
X-Mailman-Version: 2.1.22
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 Apr 2017 15:27:44 -0000
Hi I read thru the draft and yes the additional parameter in P-Served-user makes sense to better handle call diversion service. But I think a value for "orig-cdiv" may be required . e.g orig-cdiv=yes (default). though I do not have a use case for orig-cdiv=no as of now. Regards Ranjit On Fri, Mar 31, 2017 at 7:29 AM, <R.Jesske@telekom.de> wrote: > Hi Jean, > I have read Marianne's draft and support the draft to become a WG document. > Best Regards > > Roland > > -----Ursprüngliche Nachricht----- > Von: sipcore [mailto:sipcore-bounces@ietf.org] Im Auftrag von A. Jean > Mahoney > Gesendet: Donnerstag, 30. März 2017 17:22 > An: sipcore@ietf.org > Betreff: Re: [sipcore] Draft new: draft-mohali-sipcore- > originating-cdiv-parameter-00 > > Hi all, > > I mentioned this draft during the WG session today. Does anyone have any > comments on the draft? Should it become a WG document? > > Thanks! > > Jean > > On 3/12/17 4:22 PM, marianne.mohali@orange.com wrote: > > Hi all, > > > > Please find hereafter a new version of I-D, > > draft-mohali-sipcore-originating-cdiv-parameter-00 (was > > draft-mohali-dispatch-originating-cdiv-parameter-03). > > https://www.ietf.org/internet-drafts/draft-mohali-sipcore-originating- > > cdiv-parameter-00.txt > > > > Based on ADs and Chairs guidance, this draft is moved from DISPATCH > > to SIPCORE following the new charter of sipcore WG. > > > > Abstract: This specification defines a new parameter of the > > P-Served-User header field in the Session Initiation Protocol (SIP). > > This new "orig-cdiv" parameter defines the session case used by a > > proxy when handling an originating session after Call Diversion > > (CDIV) services has been invoked for the served user. The > > P-Served-User header field is defined in RFC5502 to convey the > > identity of the served user and the session case that applies to this > > particular communication session and application invocation. This > > document updates RFC5502 to add the "originating after CDIV" session > > case and to provide more guidance for using the P-Served-User header > > field in IP networks that were missing in RFC5502. > > > >> From the discussion in DISPATCH, in this version of the draft, the > >> syntax of the header could be improved as shown below: > > > > sessioncase-param = ("sescase" EQUAL ("orig" / "term")) / > > "orig-cdiv" registration-state-param = "regstate" EQUAL ("unreg" / > > "reg") > > > > This draft is not in the agenda for IETF 98 but comments are welcomed > > anyway. > > > > Best regards, Marianne > > > > > > > > > > > > ______________________________________________________________________ > > ___________________________________________________ > > > > Ce message et ses pieces jointes peuvent contenir des informations > > confidentielles ou privilegiees et ne doivent donc pas etre diffuses, > > exploites ou copies sans autorisation. Si vous avez recu ce message > > par erreur, veuillez le signaler a l'expediteur et le detruire ainsi > > que les pieces jointes. Les messages electroniques etant susceptibles > > d'alteration, Orange decline toute responsabilite si ce message a ete > > altere, deforme ou falsifie. Merci. > > > > This message and its attachments may contain confidential or > > privileged information that may be protected by law; they should not > > be distributed, used or copied without authorisation. If you have > > received this email in error, please notify the sender and delete this > > message and its attachments. As emails may be altered, Orange is not > > liable for messages that have been modified, changed or falsified. > > Thank you. > > > > _______________________________________________ sipcore mailing list > > sipcore@ietf.org https://www.ietf.org/mailman/listinfo/sipcore > > > > _______________________________________________ > sipcore mailing list > sipcore@ietf.org > https://www.ietf.org/mailman/listinfo/sipcore > > _______________________________________________ > sipcore mailing list > sipcore@ietf.org > https://www.ietf.org/mailman/listinfo/sipcore >
- [sipcore] Draft new: draft-mohali-sipcore-origina… marianne.mohali
- Re: [sipcore] Draft new: draft-mohali-sipcore-ori… A. Jean Mahoney
- Re: [sipcore] Draft new: draft-mohali-sipcore-ori… Christer Holmberg
- Re: [sipcore] Draft new: draft-mohali-sipcore-ori… DOLLY, MARTIN C
- Re: [sipcore] Draft new: draft-mohali-sipcore-ori… Andrew Allen
- Re: [sipcore] Draft new: draft-mohali-sipcore-ori… Atle Monrad
- Re: [sipcore] Draft new: draft-mohali-sipcore-ori… R.Jesske
- Re: [sipcore] Draft new: draft-mohali-sipcore-ori… Ranjit Avasarala
- Re: [sipcore] Draft new: draft-mohali-sipcore-ori… R.Jesske
- Re: [sipcore] Draft new: draft-mohali-sipcore-ori… A. Jean Mahoney