Cullen,
When we last talked, you said that your main is the fact that unreliable
responses might be sent even in the case of Require:100rel. That has now been
solved, so I am very surprised by your comments.
Also, the draft WAS back in the WG when the proposed solution was presented.
Why didn't you say anything then????
Regarding the usage, I have been provided text (mostly by Robert) regarding the
usability, limitations etc. Why haven't you said anything before if you didn't
like it????
Regards,
Christer
-----Original Message-----
From: ietf-bounces(_at_)ietf(_dot_)org
[mailto:ietf-bounces(_at_)ietf(_dot_)org] On
Behalf Of Cullen Jennings
Sent: 7. helmikuuta 2011 20:45
To: IESG IESG; ietf(_at_)ietf(_dot_)org IETF
Subject: Re: Last Call: <draft-ietf-sipcore-199-05.txt>
(Session Initiation Protocol (SIP) Response Code for
Indication of Terminated Dialog) to Proposed Standard
I was somewhat surprised to see this back in LC. I am still
not aware of any use case where this actually helps. I
searched the IETF and WG lists for email with the subject
draft-ietf-sipcore-199 and I do not see a single email that
suggests there is support for this draft or the changes in it
since the previous LC.
This draft has no use that I understand how it helps - it is
at best a very limited optimization. The SIP standards is
already too complicated with too many extensions. I believe
this draft makes SIP worse.Thought the draft mandates that
systems need to work even when the 199 are lost, I do not
think that is how the proponents of the work intent to use. I
could be very wrong but I presume that people intent to use
to control middle boxes that control media gates. It's broken
for that but given that is not discussed in the draft, it's
hard to discuss how it is broken and what would be needed to fix it.
I do not support publishing this draft as standards track
without actual WG discussion on what the problem is this
draft solves and if there is WG consensus that problem is
worth solving.
On Feb 7, 2011, at 10:02 AM, The IESG wrote:
The IESG has received a request from the Session Initiation
Protocol
Core WG (sipcore) to consider the following document:
- 'Session Initiation Protocol (SIP) Response Code for Indication of
Terminated Dialog'
<draft-ietf-sipcore-199-05.txt> as a Proposed Standard
This is the second IETF last call for this document. The
previous last call was on version -02.
While resolving review comments, an issue with the
interaction of the
199 response and the 100rel extension was identified and
addressed by
the SIPCORE working group. A full summary of the changes
are available in section 13 of the document.
The IESG plans to make a decision in the next few weeks,
and solicits
final comments on this action. Please send substantive
comments to the
ietf(_at_)ietf(_dot_)org mailing lists by 2011-02-21. Exceptionally,
comments may
be sent to iesg(_at_)ietf(_dot_)org instead. In either case, please retain
the
beginning of the Subject line to allow automated sorting.
Abstract
This specification defines a new Session Initiation Protocol (SIP)
response code, 199 Early Dialog Terminated, that a SIP
forking proxy
and a User Agent Server (UAS) can use to indicate towards upstream
SIP entities (including the User Agent Client (UAC)) that an early
dialog has been terminated, before a final response is
sent towards
the SIP entities.
The file can be obtained via
http://datatracker.ietf.org/doc/draft-ietf-sipcore-199/
IESG discussion can be tracked via
http://datatracker.ietf.org/doc/draft-ietf-sipcore-199/
No IPR declarations have been submitted directly on this I-D.
_______________________________________________
IETF-Announce mailing list
IETF-Announce(_at_)ietf(_dot_)org
https://www.ietf.org/mailman/listinfo/ietf-announce
_______________________________________________
Ietf mailing list
Ietf(_at_)ietf(_dot_)org
https://www.ietf.org/mailman/listinfo/ietf
_______________________________________________
Ietf mailing list
Ietf(_at_)ietf(_dot_)org
https://www.ietf.org/mailman/listinfo/ietf