Re: [sipcore] [stir] Fwd: New Version Notification for draft-burger-sipcore-rejected-01.txt

[Eric Burger <[e-mail]>]

Grrrr. “Tonga” = “Tolga”

> On Jul 24, 2018, at 1:48 PM, Eric Burger <[e-mail]> wrote:
> 
> Signed PGP part
> [Please keep discussion on the sipcore list. Thanks!]
> 
> Changes from -00:
> Mostly editorial, including all but one of Tonga’s suggestions and cleaning up some of the ASCII art.
> Included the Feature-Caps header in the example.
> Included an example of an audio announcement.
> 
>> Begin forwarded message:
>> 
>> From: [e-mail]
>> Subject: New Version Notification for draft-burger-sipcore-rejected-01.txt
>> Date: July 23, 2018 at 4:09:39 PM EDT
>> To: "Eric W. Burger" <[e-mail]>, "Eric Burger" <[e-mail]>
>> 
>> 
>> A new version of I-D, draft-burger-sipcore-rejected-01.txt
>> has been successfully submitted by Eric W. Burger and posted to the
>> IETF repository.
>> 
>> Name:		draft-burger-sipcore-rejected
>> Revision:	01
>> Title:		A Session Initiation Protocol (SIP) Response Code for Rejected Calls
>> Document date:	2018-07-23
>> Group:		Individual Submission
>> Pages:		15
>> URL:            https://www.ietf.org/internet-drafts/draft-burger-sipcore-rejected-01.txt
>> Status:         https://datatracker.ietf.org/doc/draft-burger-sipcore-rejected/
>> Htmlized:       https://tools.ietf.org/html/draft-burger-sipcore-rejected-01
>> Htmlized:       https://datatracker.ietf.org/doc/html/draft-burger-sipcore-rejected
>> Diff:           https://www.ietf.org/rfcdiff?url2=draft-burger-sipcore-rejected-01
>> 
>> Abstract:
>>  This document defines the 608 (Rejected) SIP response code.  This
>>  response code enables calling parties to learn their call was
>>  rejected by an intermediary and will not be answered.  As a 6xx code,
>>  the caller will be aware that future attempts to contact the same UAS
>>  will be likely to fail.  The present use case driving the need for
>>  the 608 response code is when the intermediary is an analytics
>>  engine.  In this case, the rejection is by a machine or other
>>  process.  This contrasts with the 607 (Unwanted) SIP response code,
>>  which a human at the target UAS indicated the call was not wanted.
>>  In some jurisdictions this distinction is important and may have
>>  additional requirements beyond the 607 response code.  Specifically,
>>  this document defines the use of the Call-Info header in 608
>>  responses to enable rejected callers to contact entities that blocked
>>  their calls in error.
>> 
>> 
>> 
>> 
>> Please note that it may take a couple of minutes from the time of submission
>> until the htmlized version and diff are available at tools.ietf.org.
>> 
>> The IETF Secretariat
>> 
> 
>