SIPv6 Headers and SDP Media Line Address Selection on Multihomed Hosts
draft-dmudric-sipcore-sipv6-addr-selection-00

Document Type Active Internet-Draft (individual)
Last updated 2020-01-08
Stream (None)
Intended RFC status (None)
Formats plain text pdf htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)


   SIPCORE WG                                                           
   Internet Draft                                             D. Mudric 
                                                                  Avaya 
                                                           D. Grebovich 
                                                                  Avaya 
   Expires: June 2020                                      January 2020 
    
    
     SIPv6 Headers and SDP Media Line Address Selection on Multihomed Hosts 
                     draft-dmudric-sipcore-sipv6-addr-selection-00 
    
Abstract 
    
   In the networks where multihomed hosts can have ULA and GUA addresses 
   from different ISPs, multiple SIP signaling and media connectivity 
   issues might arise due to inappropriate address selections. Some of 
   the problems are described in [RFC5220]. Since SIP and SDP allow IP 
   addresses to be embedded into their headers and lines, even if proper 
   addresses are selected initially, SIP is not equipped with the 
   mechanisms to respond to network events, and transition transport to 
   reachable addresses. As a result, SIP messages and media might be 
   filtered by routers, or discarded as unreachable destinations. 
    
   SIP protocol (RFC 3261) defines signaling messages and their headers. 
   This document describes how a multihomed host should select addresses 
   for SIP headers, like Contact and Via, to be reachable destinations. 
   Host SHOULD change a default router for uplink failures, remove 
   prefixes and addresses for unreachable ISP, and update contact 
   address list.  
    
   SDP protocol (RFC 3264) defines how participants in a session select 
   their parameters. This document describes how an offerer and answerer 
   on multihomed hosts should select their addresses. If one of the 
   selected addresses becomes unreachable, the document describes the 
   mechanism how a new one should be selected and renegotiated. 
 
 
Status of this Memo 
    
   This document is an Internet-Draft and is in full conformance with 
   all provisions of Section 10 of RFC2026 except that the right to 
   produce derivative works is not granted.  
    
   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. 
    

 
 
Mudric           Standards Track Expires - July 2020         [Page 1] 


Internet-draft SIPv6 Address Selection on Multihomed Hosts January 2020 
 
 
   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/ietf/1id-abstracts.txt 
   The list of Internet-Draft Shadow Directories can be accessed at 
        http://www.ietf.org/shadow.html. 
    
Copyright 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 
   (https://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. 
    
Conventions used in this document 
    
   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 
   "SHOULD", "SHOULD NOT", "RECOMMENDED",  "MAY", and "OPTIONAL" in this 
   document are to be interpreted as described in RFC-2119 [i]. 
    
Table of Contents 
    
   1. Introduction...................................................3 
   2. Terminology....................................................3 
   3. Problem Statement..............................................4 
      3.1 Network Topology...........................................4 
      3.1.1 Ingress filtered signaling source address & Non optimal data 
      path  6 
      3.1.2 Unreachable media destination address  7 
      3.1.3 Ingress filtered media source address  7 
      3.1.4 Unreachable listening media socket address8 
      3.1.5 Unreachable signaling ULA destination  8 
      3.1.6 Unreachable media ULA destination8 
      3.2 Background: Multi-Homed Hosts..............................8 
      3.3 Identified Problems........................................9 
      3.4 Multihomed Host Unreachable due to Uplink Failure..........9 
Show full document text