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

From: "Olle E. Johansson" <[email-masked]>
Date: Fri, 31 Jan 2014 11:49:58 +0100

Hi!
We have updated the draft to reflect the feedback we got on the list. Changes are as follows:

- Removed "Updates: 3263" from header
- Cleaned up text throughout the document to clarify the scope and intent (not to invalidate 3263-compliant implementations)
- added some TODO's based on recent comments requiring follow-up
- Slight updates to Security Considerations and Acknowledgments
- Broke Terminology and Conventions section into two separate sections

As you see we still have a todo, but we do think this is a good platform for further discussions in SIPcore.

Best regards,
/Olle & Gonzalo

Begin forwarded message:

> From: [email-masked]
> Subject: New Version Notification for draft-johansson-sip-dual-stack-02.txt
> Date: 31 Jan 2014 11:33:32 GMT+1
> 
> 
> 
> A new version of I-D, draft-johansson-sip-dual-stack-02.txt
> has been successfully submitted by Olle E. Johansson and posted to the
> IETF repository.
> 
> Name:		draft-johansson-sip-dual-stack
> Revision:	02
> Title:		Locating Session Initiation Protocol (SIP) Servers in a Dual-Stack IP Network
> Document date:	2014-01-30
> Group:		Individual Submission
> Pages:		7
> URL:            http://www.ietf.org/internet-drafts/draft-johansson-sip-dual-stack-02.txt
> Status:         https://datatracker.ietf.org/doc/draft-johansson-sip-dual-stack/
> Htmlized:       http://tools.ietf.org/html/draft-johansson-sip-dual-stack-02
> Diff:           http://www.ietf.org/rfcdiff?url2=draft-johansson-sip-dual-stack-02
> 
> Abstract:
>   RFC 3263 defines how a Session Initiation Protocol (SIP)
>   implementation, given a SIP Uniform Resource Identifier (URI), should
>   locate the next hop SIP server using Domain Name System (DNS)
>   procedures.  As SIP networks increasingly transition from IPv4-only
>   to dual-stack, a quality user experience must be ensured for dual-
>   stack SIP implementations.  This document supplements the DNS
>   procedures described in RFC 3263 for dual-stack SIP implementations
>   and ensures that they properly align to the optimizations detailed by
>   Happy Eyeballs.
> 
> 
> 
> 
> 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
>