Subject: [dispatch] Fwd: New Version Notification for draft-johansson-sip-dual-stack-00.txt

From: "Olle E. Johansson" <[email-masked]>
Date: Mon, 24 Jun 2013 10:03:31 +0200

Hi!

We have submitted a short draft that updates RFC 3263 so that dual stack SIP user agents 
have to look up both A and AAAA records. RFC 3263 suggests "A or AAAA" records.

Please give feedback and guide us through the dispatch process!

Regards,
/Olle E. Johansson

> 
> 
> 
> 
> A new version of I-D, draft-johansson-sip-dual-stack-00.txt
> has been successfully submitted by Olle E. Johansson and posted to the
> IETF repository.
> 
> Filename:	 draft-johansson-sip-dual-stack
> Revision:	 00
> Title:		 Locating SIP servers in a dual stack IP network
> Creation date:	 2013-06-24
> Group:		 Individual Submission
> Number of pages: 5
> URL:             http://www.ietf.org/internet-drafts/draft-johansson-sip-dual-stack-00.txt
> Status:          http://datatracker.ietf.org/doc/draft-johansson-sip-dual-stack
> Htmlized:        http://tools.ietf.org/html/draft-johansson-sip-dual-stack-00
> 
> 
> Abstract:
>   RFC 3263 defines how a SIP implementation given an URL should locate
>   the next hop SIP server using DNS.  The RFC repeatedly states that
>   the implementation should look up IPv4 or IPv6 addresses, which is
>   not a good solution considering the issues that lead to the
>   development of Happy Eyeballs (RFC XXX).  This document corrects this
>   behaviour for dual stack SIP implementations so that an
>   implementation so that an implementation should look up both IPv4 and
>   IPv6 addresses.  This way, the implementation can find the best
>   network flow and have a greater chance in success in reaching the
>   service.
> 
>   This document also clarifies DNS SRV usage for single stack clients.
>