Internet-Draft submission

idnits 2.16.04 

/a/www/www6s/staging/draft-ietf-sipcore-450-00.txt:

  Showing Errors (**), Flaws (~~), Warnings (==), and Comments (--).
  Errors MUST be fixed before draft submission.  Flaws SHOULD be fixed before draft submission.

  Checking boilerplate required by RFC 5378 and the IETF Trust (see
  https://trustee.ietf.org/license-info):
  ----------------------------------------------------------------------------

     No issues found here.

  Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt:
  ----------------------------------------------------------------------------

     No issues found here.

  Running in submission checking mode -- *not* checking nits according to
  https://www.ietf.org/id-info/checklist .
  ----------------------------------------------------------------------------


     No nits found.

INTERNET-DRAFT                                                  R. Myers
                                                                S. Smith
Intended Status:Proposed Standard                            Capital One
Expires: March 2020                                       September 2019


          Session Initiation Protocol (SIP) Response Code For
                          All Routes Exhausted
			draft-ietf-sipcore-450-00.txt


Abstract

   This document specifics a new Session Initiation Protocol (SIP)
   response code of "450 All Routes Exhausted". This response code
   should be used to inform a UAC (User Agent Client) that a UAS (User
   Agent Server)or Proxy device has initiated a dialog request on behalf
   of a UAC (User Agent Client) to multiple destinations and that none
   of those destinations were able to fulfil the initial dialog request.


Status of this Memo

   This Internet-Draft is submitted to IETF in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF), its areas, and its working groups.  Note that
   other groups may also distribute working documents as
   Internet-Drafts.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   The list of current Internet-Drafts can be accessed at
   http://www.ietf.org/1id-abstracts.html

   The list of Internet-Draft Shadow Directories can be accessed at
   http://www.ietf.org/shadow.html











R. Myers, et. al.         Expires January 2020                  [Page 1]
INTERNET DRAFT           SIP Response Code 450            September 2019


Copyright and License Notice

   Copyright (c) 2019 IETF Trust and the persons identified as the
   document authors. All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document. Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document. Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.



Table of Contents

   1  Introduction  . . . . . . . . . . . . . . . . . . . . . . . . .  3
     1.1  Terminology . . . . . . . . . . . . . . . . . . . . . . . .  3
     4.  User Agent Client behavior . . . . . . . . . . . . . . . . .  4
     4.1.  Examples of resource types . . . . . . . . . . . . . . . .  5
     4.2.  Examples of policy procedures  . . . . . . . . . . . . . .  6
   5.  User Agent Server behavior . . . . . . . . . . . . . . . . . .  7
   6.  Proxy behavior . . . . . . . . . . . . . . . . . . . . . . . .  8
   7.  Backward compatibility . . . . . . . . . . . . . . . . . . . .  9
   8.  199 Early Dialog Terminated  . . . . . . . . . . . . . . . . .  9
   9.  Usage with SDP offer/answer  . . . . . . . . . . . . . . . . . 10
   10. Usage with 100rel  . . . . . . . . . . . . . . . . . . . . . . 10
   11. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
     11.1. Example with a forking proxy which generates 199 . . . . . 10
     11.2. Example with a forking proxy which receives 200 OK . . . . 11
     11.3. Example with two forking proxies, of which one
           generates 199  . . . . . . . . . . . . . . . . . . . . . . 12
   3  Security Considerations . . . . . . . . . . . . . . . . . . . .  5
   4  IANA Considerations . . . . . . . . . . . . . . . . . . . . . .  5
     4.1  IANA Registration of the 450 Response Code  . . . . . . . .  5
     4.2  IANA Registration of the 450 All Routes Exhausted . . . . .  5
   5  References  . . . . . . . . . . . . . . . . . . . . . . . . . .  5
     5.1  Normative References  . . . . . . . . . . . . . . . . . . .  5
     5.2  Informative References  . . . . . . . . . . . . . . . . . .  5
   Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . .  6








R. Myers, et. al.         Expires January 2020                  [Page 2]