[sipcore] Mirja Kühlewind's Yes on draft-ietf-sipcore-dns-dual-stack-07: (with COMMENT)

"Mirja Kuehlewind" <ietf@kuehlewind.net> Mon, 15 August 2016 13:16 UTC

Return-Path: <ietf@kuehlewind.net>
X-Original-To: sipcore@ietf.org
Delivered-To: sipcore@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 4D91A12D8C9; Mon, 15 Aug 2016 06:16:32 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Mirja Kuehlewind <ietf@kuehlewind.net>
To: The IESG <iesg@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.29.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <147126699230.31678.9613693360268273574.idtracker@ietfa.amsl.com>
Date: Mon, 15 Aug 2016 06:16:32 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/sipcore/YAgXz28cG3ZVCV9D8KBZ3MFuBxU>
Cc: sipcore@ietf.org, draft-ietf-sipcore-dns-dual-stack@ietf.org, sipcore-chairs@ietf.org
Subject: [sipcore] Mirja Kühlewind's Yes on draft-ietf-sipcore-dns-dual-stack-07: (with COMMENT)
X-BeenThere: sipcore@ietf.org
X-Mailman-Version: 2.1.17
List-Id: SIP Core Working Group <sipcore.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sipcore>, <mailto:sipcore-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sipcore/>
List-Post: <mailto:sipcore@ietf.org>
List-Help: <mailto:sipcore-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sipcore>, <mailto:sipcore-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 15 Aug 2016 13:16:32 -0000

Mirja Kühlewind has entered the following ballot position for
draft-ietf-sipcore-dns-dual-stack-07: Yes

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-sipcore-dns-dual-stack/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

Thanks! This seems very useful in the preparation for Happy-Eyeballs.

One question: Why does a client need to look up ALL addresses if it
already knows that it itself only support one specific address familiy?

And related to this question: Shouldn't it be named "multi-stack client"
instead of "dual-stack client"?