1 IETF 72 BLISS WG meeting draft-ietf-bliss-ach-analysis-02 John Elwell.

Slides:



Advertisements
Similar presentations
1 © 2001, Cisco Systems, Inc. All rights reserved. © 2004, Cisco Systems, Inc. All rights reserved. Location Conveyance in SIP draft-ietf-sipping-location-requirements-02.
Advertisements

August 2, 2005SIPPING WG IETF 63 ETSI TISPAN ISDN simulation services Roland Jesske Denis Alexeitsev Miguel Garcia-Martin.
Indication of support for keep- alive draft-holmberg-sip-keep-03 Christer Holmberg
IETF 71 SIPPING WG meeting draft-ietf-sipping-pai-update-00.
July 13, 2006SIPPING WG IETF 66Slide # 1 ETSI TISPAN call completion services (draft-poetzl-sipping-call-completion-00) Roland
RFC 3489bis Jonathan Rosenberg Cisco Systems. Technical Changes Needed Allow STUN over TCP –Driver: draft-ietf-sip-outbound Allow response to omit CHANGED-
Service Identification Jonathan Rosenberg Cisco. Agenda Service Identification Architecture draft (draft-rosenberg-sipping-service- identification) Media.
Remote Call/Device Control IETF82, Dispatch WG, Taipei November 15, Rifaat Shekh-Yusef Cullen Jennings Alan Johnston.
SIP Working Group Stuff Jonathan Rosenberg dynamicsoft.
Identifying intra-realm calls with explicit addressing realm identifier attribute François AUDET SIPPING WG Meeting IETF-57.
IETF DMM WG Mobility Exposure and Selection WT Report Alper Yegin, on behalf of the WT IETF 92.
GRUU Mechanism Jonathan Rosenberg. Status Draft-rosenberg-sipping-gruu-reqs-01 defines the problem Draft-rosenberg-sip-gruu submitted with proposed solution.
July 30, 2010SIPREC WG1 SIP Call Control - Recording Extensions draft-johnston-siprec-cc-rec-00 Alan Johnston Andrew Hutton.
What is a SIP Trunk Anyway?!? Jonathan Rosenberg Cisco.
Overload in SIP Jonathan Rosenberg Cisco Systems.
SIP Action Referral Rifaat Shekh-Yusef Cullen Jennings Alan Johnston Francois Audet 1 IETF 80, SPLICES WG, Prague March 29, 2011.
Request History – Solution Mary Barnes SIP WG Meeting IETF-57 draft-ietf-sip-history-info-00.txt.
1 RTCWEB interim Remote recording use case / requirements John Elwell.
History of Voic Cullen Jennings Mary Barnes.
Draft-audet-sipping-feature-ref Feature Referral in the Session Initiation Protocol (SIP) draft-audet-sipping-feature-ref-00 François Audet -
Draft-thomson-geopriv-res-gw-lis-discovery Ray Bellis Nominet UK IETF79.
MINT Working Group Jan 9-10 at Harris FBC Melbourne, FL.
@ IETF 68. Note Well Any submission to the IETF intended by the Contributor for publication as all or part of an IETF Internet-Draft or RFC and any statement.
1 Path-decoupled signaling - towards a BOF in SF NSIS working group context Path-decoupled signalling - definition –Path-oriented.
XCAP Needed Diffs Jonathan Rosenberg Cisco Systems.
IETF 77 MARTINI WG draft-ietf-martini-reqs-02 John Elwell Hadriel Kaplan (editors)
Access and Query Task Force Status at F2F1 Simon Miles.
Draft-elwell-sipping- redirection-reason-00 Author: John Elwell
BLISS Problem Statement Jonathan Rosenberg Cisco.
19 March 2003draft-burger-sipping-netann-05.txt1 Network Announcements with SIP IETF 56 Eric Burger
SIP Interconnect Guidelines draft-hancock-sip-interconnect-guidelines-01 David Hancock, Daryl Malas.
SIP INFO Event Framework (draft-kaplan-sip-info-events-00) Hadriel Kaplan Christer Holmberg 70th IETF, Vancouver, Canada.
SIPREC draft-ietf-siprec-req-05 Requirements for Media Recording using SIP Draft authors: K. Rehor, A. Hutton, L. Portman, R. Jain, H. Lum IETF 79.1 Interim.
SIP working group IETF#70 Essential corrections Keith Drage.
Access and Query Task Force Status at F2F1 Simon Miles.
1 IETF 76 Hiroshima DISPATCH WG SIP Alert-Info URN draft-liess-dispatch-alert-info-urns-00 Denis Alexeitsev Laura Liess
SIP Extensions for Network-Asserted Caller Identity and Privacy within Trusted Networks Flemming Andreasen W. Marshall, K. K. Ramakrishnan,
SIP WG Open Issues IETF 50 Jonathan Rosenberg dynamicsoft.
Open issues from SIP list Jonathan Rosenberg dynamicsoft.
Name that User John Elwell Cullen Jennings Venkatesh Venkataramanan
GRUU Jonathan Rosenberg Cisco Systems. Changes in -06 Editorial as a result of RFC-ED early copy experiment.
1 CPCP Hisham Khartabil XCON WG IETF 59, Seoul
SIP Events: Changes and Open Issues IETF 50 / SIP Working Group Adam Roach
Outbound draft-ietf-sip-outbound-01 Cullen Jennings.
Slide #1 Nov 6 -11, 2005SIP WG IETF64 Feature Tags with SIP REFER draft-ietf-sip-refer-feature-param-00 Orit
Caller Preferences Jonathan Rosenberg dynamicsoft.
History-Info header and Support of target-uri Solution Requirements Mary Barnes Francois Audet SIPCORE.
March 20th, 2001 SIP WG meeting 50th IETF SIP WG meeting Overlap signalling handling
The “application” Profile Type (draft-channabasappa-sipping-app-profile-type-01) Sumanth Channabasappa Josh Littlefield Salvatore Loreto 70th IETF, Vancouver,
SIPPING Drafts Jonathan Rosenberg dynamicsoft. Conferencing Package Issues Only one – scope Depends on broader work in conferencing May include –Participant.
SIP Working Group IETF 72 chaired by Keith Drage, Dean Willis.
CSI WG / IETF741/12 Implementation of SeND/CGA and Extensions Beijing University of Posts and Telecommunications HUAWEI.
Mapping and interworking of Diversion information between Diversion and History-Info Headers in the SIP draft-mohali-bliss-diversion-history-info-00 draft-mohali-bliss-diversion-history-info-00.
PANA in DSL networks draft-morand-pana-panaoverdsl-00.txt Lionel Morand Roberta Maglione John Kaippallimalil Alper Yegin IETF-67, San Diego.
SIP wg Items Jonathan Rosenberg dynamicsoft Caller Preferences: Changes Discussion of Redirects –Previous draft only proxy –Nothing different for redirect.
ID Tracker States: An Internet Draft’s Path Through the IESG
Request History Capability – Requirements & Solution
Kumiko Ono End-to-middle Security in SIP draft-ietf-sipping-e2m-sec-reqs-04 draft-ono-sipping-end2middle-security-03 Kumiko Ono.
SIP Configuration Issues: IETF 57, SIPPING
Request-URI Param Delivery
Requirements and Implementation Options for the Multiple Line Appearance Feature using the Session Initiation Protocol (SIP) draft-johnston-bliss-mla-req-00.
SIP Identity issues John Elwell, Jonathan Rosenberg et alia
Network Announcements with SIP
call completion services
draft-barth-pce-association-bidir-01
Event Notification in SIP SUBSCRIBE and NOTIFY and an example service
A YANG Data Model for Microwave Radio Link draft-mwdt-ccamp-mw-yang-00
SIP Session Timer Glare Handling
Rifaat Shekh-Yusef IETF105, OAuth WG, Montreal, Canada 26 July 2019
M. Boucadair, J. Touch, P. Levis and R. Penno
Presentation transcript:

1 IETF 72 BLISS WG meeting draft-ietf-bliss-ach-analysis-02 John Elwell

2 Measures to be taken (1) Addressing conflict between UA and proxy –The present draft proposes configuration of UAs to get them to defer to a proxy for ACH –Does not mandate a particular configuration method, but suggests the configuration framework be one method –Proposes draft-petrie-sipping-voip-features-dataset (assuming it is adopted as work item) be enhanced to include this parameter –Open issue over whether one parameter is sufficient or if several are needed (to cover different conditions) –PROPOSAL – go ahead and ask SIPPING to add single parameter to voip-features-dataset

3 Measures to be taken (2) Obtaining information from UA for ACH at proxy –Proposes conditions: busy explicit rejection silent rejection –Proposes scopes: local (only current branch and other branches to same user, but not voic or other users) everything, including voic and other users

4 Measures to be taken (2, continued) Proposed response codes –Busy / local: 486 –Explicit rejection / local: 480 –Silent rejection / local: 487 (i.e., as if proxy had issued CANCEL request) –Busy / global: 600 –Explicit rejection / global: 603 –Silent rejection / global: No code recommended 486/480/600/603 may be accompanied by Retry-After Open issue over 480 for explicit rejection / local –(RFC 3261 suggests this for DND, but concern about overload with edge proxy indicating temporary lack of resources) Open issue over need for code for silent rejection / global –Perhaps for SPIT, but is this more a RUCUS topic?

5 Measures to be taken (3) Scope of 6xx response codes –Propose not to alter present meaning of 6xx (truly global) –If something less than global required, then use 4xx/5xx

6 Measures to be taken (4) Configuring ACH at the proxy from the UA –XCAP (some consider this overkill) –Proposal from Jonathan Rosenberg for a trivial REST Representational State Transfer) interface, e.g: POST Would need to be extensible How would this be standardised, and where? Lack of list discussion on this topic Any interest in investigating a REST-based solution?