Re: [sipcore] Spencer Dawkins' Yes on draft-ietf-sipcore-dns-dual-stack-07: (with COMMENT)
Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com> Fri, 19 August 2016 20:15 UTC
Return-Path: <spencerdawkins.ietf@gmail.com>
X-Original-To: sipcore@ietfa.amsl.com
Delivered-To: sipcore@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 819A612D9AB; Fri, 19 Aug 2016 13:15:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dt0zUW1JLTEY; Fri, 19 Aug 2016 13:15:06 -0700 (PDT)
Received: from mail-yw0-x22e.google.com (mail-yw0-x22e.google.com [IPv6:2607:f8b0:4002:c05::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 33A2E12D66C; Fri, 19 Aug 2016 13:10:47 -0700 (PDT)
Received: by mail-yw0-x22e.google.com with SMTP id z8so19496256ywa.1; Fri, 19 Aug 2016 13:10:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=pKZ16yCdG/4nWHUVWAocO+gbF57I/ADYuUga96PDui4=; b=VX4L6hKH/eRpnL1PfYv+H4DEOQuPxS6jT+uHoADu0ziTqApxdJqQUxlfS/ucyRwB/B BLYoM89Yjt8Tv1E+wRlAceUSW7LENgXdoE+MJwuVHlq1A5dYVL1W2/dEXEBBJnNPW9q2 m+/tbbyIV0tNmhkC+pl6SSK7QmBiJsDKIdA/ej7gyWIR/vsSjjCUR/wjemRonwMXWsmZ e8SLd/vBvVgHd8qQ7xs7Hclc6GP3zT2C47FXu/JnVUxBhYy9Zwg2bf9TtGT0TRsnenHd TleoPtg/8hSscQNyY74K2B7cyeI4o/sU2WoXI89ynjLGi0SWQpQmZQGPjt4VHx/va/Cm AvIw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=pKZ16yCdG/4nWHUVWAocO+gbF57I/ADYuUga96PDui4=; b=BB2ozu3V5B/MzDCOoz+K3izGAZlrdLmE/S/PTM1IV+9rfMz49RQHiGvelQQAeLHYGx ZpsWhXZUaOUPhXgTuQUC8CUhK5Txc6USdhbrMeUYmz1E2AyvNLtA97zDM9j6L+HLJTdq F3YozEscVGgi7qjMkp5E4BzLgG5jzwKBPrl/wFSmiRXUUxdqVdTQ5QZnO4UU8drmWrdg Gn48UOimk3DqOB5V3e9JQ6/y0Kikep4Xx22hToxPrXWY9moDeBrfbBAhHJwtyWBdKvD5 avGul4JF9ibpqTfSOcYCZHa541iaH4zlg0I79pfs1Z44mBnNF/2tjscCCUV1OIzXEmoF rtbw==
X-Gm-Message-State: AEkooutqfS3W/wYDRu5bKyYkGdvcyjeHcHAZm3M4Xlkf0E+F8Pf33qqVXr79p1Cqs6VpdJdhqJTcCDyhXmIRkA==
X-Received: by 10.129.93.86 with SMTP id r83mr7947077ywb.211.1471637446473; Fri, 19 Aug 2016 13:10:46 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.37.210.195 with HTTP; Fri, 19 Aug 2016 13:10:46 -0700 (PDT)
In-Reply-To: <87mvk87esk.fsf@hobgoblin.ariadne.com>
References: <147140468741.19939.3811368106001545602.idtracker@ietfa.amsl.com> <87mvk87esk.fsf@hobgoblin.ariadne.com>
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Date: Fri, 19 Aug 2016 15:10:46 -0500
Message-ID: <CAKKJt-c+H7h+OnoxOzcn59F6qsKz_aVg_ah+Rpy6kpaw8AJUpg@mail.gmail.com>
To: "Dale R. Worley" <worley@ariadne.com>
Content-Type: multipart/alternative; boundary="001a114d805c3c3c97053a724bdf"
Archived-At: <https://mailarchive.ietf.org/arch/msg/sipcore/NLyBdkASjWUR7eMFE-nloBRTg-8>
Cc: SIPCORE <sipcore@ietf.org>, draft-ietf-sipcore-dns-dual-stack@ietf.org, "iesg@ietf.org" <iesg@ietf.org>, sipcore-chairs@ietf.org
Subject: Re: [sipcore] Spencer Dawkins' Yes on draft-ietf-sipcore-dns-dual-stack-07: (with COMMENT)
X-BeenThere: sipcore@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
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: Fri, 19 Aug 2016 20:15:08 -0000
Hi, Dale, On Fri, Aug 19, 2016 at 2:13 PM, Dale R. Worley <worley@ariadne.com> wrote: > "Spencer Dawkins" <spencerdawkins.ietf@gmail.com> writes: > > Could you provide some explanation for the reader as to why SIP is > > "different", following this statement? Even an example would be useful. > > > > Unfortunately, in common SIP situations, it is not possible to "race" > > simultaneous request attempts using two address families. > > That's a good point, because the reason is non-obvious to a reader who > hasn't hassled with SIP in unreliable network environments. > > Racing in HTTP is the sending of simultaneous TCP SYNs to two different > addresses. The client then continues the handshake and sends the > request to the address that responds first. The crucial fact is that > opening a TCP connection to an HTTP server alone does not change the > server's state. > > SIP requests are usually transmitted as single UDP packets, so sending > two copies of the request to two different addresses risks having two > copies of the request propagating through the SIP network at the same > time -- the difference from HTTP is that the SIP element cannot test the > route in a non-state-changing way. > > If two copies of the same request arrive at one client, the client must > reject the second of them with a 482 response. But this rule is not > sufficient to prevent user-visible differences in behavior because a > proxy that is upstream of the second request to arrive at the client may > (almost immediately!) serially fork the second request to further > destinations. A version of this scenario that I saw in the wild is > diagrammed in > https://www.ietf.org/mail-archive/web/sipcore/current/msg06853.html. > > I've added this explanation to section 3.2. You can see the change in > > https://www.ietf.org/rfcdiff?url1=draft-ietf-sipcore-dns- > dual-stack-07&url2=http://svn.resiprocate.org/rep/ietf- > drafts/worley/draft-ietf-sipcore-dns-dual-stack-08.txt > > Dale > That's a terrific response to my comment. Thank you for including your response in the document! Spencer
- Re: [sipcore] Spencer Dawkins' Yes on draft-ietf-… Spencer Dawkins at IETF
- Re: [sipcore] Spencer Dawkins' Yes on draft-ietf-… Dale R. Worley
- [sipcore] Spencer Dawkins' Yes on draft-ietf-sipc… Spencer Dawkins