IETF Logo Mail Archive

Re: [straw] WGLC for draft-ietf-straw-sip-traceroute-01.txt

Hadriel Kaplan <hadriel.kaplan@oracle.com> Mon, 10 March 2014 17:09 UTC

Return-Path: <hadriel.kaplan@oracle.com>
X-Original-To: straw@ietfa.amsl.com
Delivered-To: straw@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 870B91A052E for <straw@ietfa.amsl.com>; Mon, 10 Mar 2014 10:09:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.748
X-Spam-Level:
X-Spam-Status: No, score=-4.748 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.547, SPF_PASS=-0.001] autolearn=ham
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 4Wlb_y49ZqZN for <straw@ietfa.amsl.com>; Mon, 10 Mar 2014 10:09:11 -0700 (PDT)
Received: from aserp1040.oracle.com (aserp1040.oracle.com [141.146.126.69]) by ietfa.amsl.com (Postfix) with ESMTP id 20FEC1A04B7 for <straw@ietf.org>; Mon, 10 Mar 2014 10:09:11 -0700 (PDT)
Received: from acsinet21.oracle.com (acsinet21.oracle.com [141.146.126.237]) by aserp1040.oracle.com (Sentrion-MTA-4.3.2/Sentrion-MTA-4.3.2) with ESMTP id s2AH95dC004665 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 10 Mar 2014 17:09:05 GMT
Received: from aserz7022.oracle.com (aserz7022.oracle.com [141.146.126.231]) by acsinet21.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id s2AH94s2004871 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 10 Mar 2014 17:09:04 GMT
Received: from abhmp0012.oracle.com (abhmp0012.oracle.com [141.146.116.18]) by aserz7022.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id s2AH94NY028806; Mon, 10 Mar 2014 17:09:04 GMT
Received: from [10.0.1.12] (/66.31.4.61) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Mon, 10 Mar 2014 10:09:04 -0700
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
From: Hadriel Kaplan <hadriel.kaplan@oracle.com>
In-Reply-To: <4A4F136CBD0E0D44AE1EDE36C4CD9D9973914B4F@VOEXM31W.internal.vodafone.com>
Date: Mon, 10 Mar 2014 13:09:02 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <A43C01B2-7049-4977-9922-C4F78FD411AD@oracle.com>
References: <4A4F136CBD0E0D44AE1EDE36C4CD9D9973905789@VOEXM31W.internal.vodafone.com> <41F7292D-28D8-4192-A4BF-22738BF3939D@oracle.com> <4A4F136CBD0E0D44AE1EDE36C4CD9D9973914B4F@VOEXM31W.internal.vodafone.com>
To: "Dawes, Peter, Vodafone Group" <Peter.Dawes@vodafone.com>
X-Mailer: Apple Mail (2.1874)
X-Source-IP: acsinet21.oracle.com [141.146.126.237]
Archived-At: http://mailarchive.ietf.org/arch/msg/straw/JKuaIO3k6apCkFjUFJmFK7snTi0
Cc: "straw@ietf.org" <straw@ietf.org>
Subject: Re: [straw] WGLC for draft-ietf-straw-sip-traceroute-01.txt
X-BeenThere: straw@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Sip Traversal Required for Applications to Work \(STRAW\) working group discussion list" <straw.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/straw>, <mailto:straw-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/straw/>
List-Post: <mailto:straw@ietf.org>
List-Help: <mailto:straw-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/straw>, <mailto:straw-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 10 Mar 2014 17:09:15 -0000

Hi Peter,
sorry for the delay in responding to this!
comments inline...

On Dec 17, 2013, at 7:04 AM, Dawes, Peter, Vodafone Group <Peter.Dawes@vodafone.com> wrote:

> I think the draft text in clause 3.1 Processing a Received Max-Forwards Header Field (lines 206 - 208)] "As currently defined in [RFC3261], the UAS half of a B2BUA does not technically need to inspect the Max-Forwards header field value for received requests - only Proxies do." should be clearer in terms of what the implementer actually has to do. 

It says:
   As currently defined in [RFC3261], the UAS half of a B2BUA does not
   technically need to inspect the Max-Forwards header field value for
   received requests - only Proxies do.  This behavior was updated by
   [draft-loop-detection], such that a compliant B2BUA needs to both
   inspect the value in order to prevent loops, as well as copy and
   decrement the value as if it were a Proxy.  This document also
   requires such behavior in order to succeed, therefore a B2BUA
   supporting the traceroute mechanism defined in this document MUST
   also comply with [draft-loop-detection].


How is that not clear?


> You replied that "...I think it is in fact in doubt.  I know of many B2BUAs which do in fact decrement max-forwards. (and I think they're right to)". So what does the implementer do? Be happy that they might not need to change too much? Make sure all of their B2BUAs decrement Max-Forwards whether they will loopback media or not? Be aware that if they don't want their B2BUA to decrement Max-Forwards then they can't use this mechanism? Something else?

See above.

-hadriel

v2.23.0 | Report a Bug | By Email