Re: [sipcore] IETF#98: SIPCORE notes (Christer)
"A. Jean Mahoney" <mahoney@nostrum.com> Wed, 19 April 2017 15:59 UTC
Return-Path: <mahoney@nostrum.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 EF8C8129B04 for <sipcore@ietfa.amsl.com>; Wed, 19 Apr 2017 08:59:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.88
X-Spam-Level:
X-Spam-Status: No, score=-1.88 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01, 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 h9hqYxPHl1yA for <sipcore@ietfa.amsl.com>; Wed, 19 Apr 2017 08:59:04 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (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 AF1D2129577 for <sipcore@ietf.org>; Wed, 19 Apr 2017 08:59:04 -0700 (PDT)
Received: from mutabilis-2.local ([47.186.26.91]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id v3JFx2OR029500 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO) for <sipcore@ietf.org>; Wed, 19 Apr 2017 10:59:03 -0500 (CDT) (envelope-from mahoney@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host [47.186.26.91] claimed to be mutabilis-2.local
To: sipcore@ietf.org
References: <7594FB04B1934943A5C02806D1A2204B4CB4C731@ESESSMB109.ericsson.se> <0ab1c9cd-58f3-3b41-d286-f3865f54cec0@nostrum.com>
From: "A. Jean Mahoney" <mahoney@nostrum.com>
Message-ID: <ff6e86b7-c968-483a-c5d0-79e962bfa9a3@nostrum.com>
Date: Wed, 19 Apr 2017 10:59:02 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.0.1
MIME-Version: 1.0
In-Reply-To: <0ab1c9cd-58f3-3b41-d286-f3865f54cec0@nostrum.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/sipcore/7dHIjnxyDxNCDWTsCExvV457oeU>
Subject: Re: [sipcore] IETF#98: SIPCORE notes (Christer)
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: Wed, 19 Apr 2017 15:59:07 -0000
Since there have been no comments, I'll be uploading these notes as the minutes. Thanks again, Christer! Jean On 4/5/17 3:12 PM, A. Jean Mahoney wrote: > Thank you for the notes, Christer! > > Session participants, please review and send any corrections to the list. > > Jean > > > On 4/5/17 2:05 PM, Christer Holmberg wrote: >> Hi, >> >> Below are my notes from the SIPCORE session. >> >> Regards, >> >> Christer >> >> --------------------------------------------------------------------------- >> >> >> *Topic: SIP Call-Info Parameters for Labeling Calls* >> >> *Presenter: Henning Schulzrinne* >> >> *Draft: draft-ietf-sipcore-callinfo-spam-00* >> >> What is it? >> >> -Defines SIP Call-Info parameters and a feature tag that allow >> originating, intermediate and terminating SIP entities to label calls >> as to their type, spam probability and references to additional >> information. >> >> Presentation in a nutshell? >> >> -Generic presentation about robocalls. >> >> -Some are illegal, some are legal but unwanted, and some are >> wanted/helpful. >> >> -Call filtering can be done by carriers themselves, by carriers using >> third-party tools, or by a device itself. >> >> -Presentation of new SIP Call-Info header field parameters and an >> associated feature capability indicator. >> >> What did people say? >> >> -It was asked whether it would be better to insert the information in >> the STIR PASSPortT structure instead. Indicated that it could be part >> of PASSPorT in the future. >> >> Ok, so what next? >> >> -Additional comments are welcome. >> >> -ACTION POINT: Christer H and Paul K will review the feature >> capability indicator. >> >> ------------ >> >> *Topic: Location Source Parameter for the SIP >> Geolocation Header Field* >> >> *Presenter: Roland Jesske* >> >> *Draft: draft-winterbottom-sipcore-locparam-00* >> >> What is it? >> >> -Adds parameter to the Geolocation header field values to indicate the >> node that added the value. >> >> Presentation in a nutshell? >> >> -Indicated that the feature is required by ETSI M/493 in order to >> assist downstream nodes. >> >> -Proposed to adopt the draft by the SIPCORE WG and initiate WGLC. >> >> What did people say? >> >> -Some had issues with the use of domain name to indicate nodes. >> >> -The chairs asked people to review the draft. >> >> Ok, so what next? >> >> -The discussion will continue on the mailing list. >> >> *Topic: Third-Party Authentication for Session >> Initiation Protocol (SIP)* >> >> *Presenter: Rifaat Shekh-Yusef* >> >> *Draft: draft-yusef-sipcore-sip-authn-01* >> >> What is it? >> >> -Authentication mechanism for SIP, that is based on the OAuth 2.0 and >> OpenID Connect Core 1.0 specifications. >> >> Presentation in a nutshell? >> >> -Difference between the draft and a previous draft. The new draft is a >> scaled down version, where previously controversial parts have been >> removed. >> >> What did people say? >> >> -Jon Peterson, who raised issues on the previous draft, indicated that >> he has some minor issues, but that he is ok with the scope of the >> draft and moving it forward. >> >> Ok, so what next? >> >> -The chairs did a hum regarding taking on the work. >> >> -OUTCOME: There was a clear consensus for taking on the work. >> >> *Topic: ISUP Cause Location Parameter for the SIP >> Reason Header Field* >> >> *Presenter: Roland Jesske* >> >> *Draft: draft-jesske-sipcore-reason-q850-loc-00* >> >> -The draft had previously been discussed in DISPATCH (see notes for >> more information), where it was decided to move the draft to the >> SIPCORE WG and let SIPCORE decided on whether take on the work. >> >> Ok, so what next? >> >> -The chairs did a hum regarding taking on the work. >> >> -OUTCOME: There was a clear consensus for taking on the work. >> >> *Topic: The Session Initiation Protocol (SIP) Digest >> Authentication Scheme* >> >> *Presenter: Rifaat Shekh-Yusef* >> >> *Draft: draft-yusef-sipcore-digest-scheme-05* >> >> What is it? >> >> -Updates the Digest Access Authentication scheme used by the Session >> Initiation Protocol (SIP) to add support for SHA2 digest algorithms to >> replace the MD5 algorithm >> >> Presentation in a nutshell? >> >> -Background what has happened for HTTP, and to apply the same for SIP. >> >> -Indicated that forking could potentially cause problems, if multiple >> servers are to be authenticated by the client. >> >> What did people say? >> >> -It was questioned whether there is a need for a UA to authenticate >> multiple servers. It was indicated that it would be problematic with >> current behaviour of forking proxies. Nobody could identity a case >> where it would be needed. >> >> -Indicated that similar algorithm update is also done for STUN, so the >> author was advised to take a look at the STUNbis draft. >> >> Ok, so what next? >> >> -No decision was made. Discussions will continue on the list. >> >> >> >> _______________________________________________ >> 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
- Re: [sipcore] IETF#98: SIPCORE notes (Christer) A. Jean Mahoney
- [sipcore] IETF#98: SIPCORE notes (Christer) Christer Holmberg
- Re: [sipcore] IETF#98: SIPCORE notes (Christer) A. Jean Mahoney