Re: [sipcore] draft-ietf-sipcore-rfc4244bis-callflows-07: comments
Mary Barnes <mary.ietf.barnes@gmail.com> Tue, 22 October 2013 13:13 UTC
Return-Path: <mary.ietf.barnes@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 8AD5111E8378 for <sipcore@ietfa.amsl.com>; Tue, 22 Oct 2013 06:13:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.398
X-Spam-Level:
X-Spam-Status: No, score=-102.398 tagged_above=-999 required=5 tests=[AWL=0.201, BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Gb9dEY2Q-TO7 for <sipcore@ietfa.amsl.com>; Tue, 22 Oct 2013 06:13:48 -0700 (PDT)
Received: from mail-we0-x22c.google.com (mail-we0-x22c.google.com [IPv6:2a00:1450:400c:c03::22c]) by ietfa.amsl.com (Postfix) with ESMTP id 6F46311E846A for <sipcore@ietf.org>; Tue, 22 Oct 2013 06:13:43 -0700 (PDT)
Received: by mail-we0-f172.google.com with SMTP id q58so8155432wes.31 for <sipcore@ietf.org>; Tue, 22 Oct 2013 06:13:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=QozJtkqY2WOZ+W4/BjAutApVmnuPwF35Z+6mzKBahog=; b=YTt/Etgm3/6+QcEeBnnrFaYUKvO0vH3e/3cU+aY3aMUOP838jUbXTCP759SpGWPuU/ 0rR5ONpr4PPK5C/KRtKeZf41LO9je/BH4OsIV42RI8PPChmYT2o+ZRJKe0TVQVB/1HFv i0IvQg7nHwIGKbamgC2Pll3n3IdOKJ0NnT7s4lHQMR0QUDTYmr/ePij8846/Bu+jY4H/ O9LmmvPMqQuEoB/NT0+CJ2XNHGTh+/aXcNDvhVB7JrRNyEjdXm8fPAjVcaAGmQ+FfGoQ 7tuopN+R7MtRe6niXMY+F8gk2bkv/KTYeqFXlI4uDqIczSVxVYQntnk4aio8mL4mZKtw 3gwQ==
MIME-Version: 1.0
X-Received: by 10.180.187.41 with SMTP id fp9mr14385010wic.33.1382447622507; Tue, 22 Oct 2013 06:13:42 -0700 (PDT)
Received: by 10.216.36.4 with HTTP; Tue, 22 Oct 2013 06:13:42 -0700 (PDT)
In-Reply-To: <576A8B541C219D4E9CEB1DF8C19C7B881A065A5E@MBX08.citservers.local>
References: <576A8B541C219D4E9CEB1DF8C19C7B881A065A5E@MBX08.citservers.local>
Date: Tue, 22 Oct 2013 08:13:42 -0500
Message-ID: <CAHBDyN5QJwu-yd7b1HtqG0RJKOCefVoNGAjVSf0mgBuAbcgxjQ@mail.gmail.com>
From: Mary Barnes <mary.ietf.barnes@gmail.com>
To: Brett Tate <brett@broadsoft.com>
Content-Type: multipart/alternative; boundary="001a11c3844c75d0c704e9542b15"
Cc: "draft-ietf-sipcore-rfc4244bis-callflows@tools.ietf.org" <draft-ietf-sipcore-rfc4244bis-callflows@tools.ietf.org>, "sipcore@ietf.org" <sipcore@ietf.org>
Subject: Re: [sipcore] draft-ietf-sipcore-rfc4244bis-callflows-07: comments
X-BeenThere: sipcore@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Tue, 22 Oct 2013 13:13:48 -0000
Brett, Thanks very much for your careful review. We will fix those errors and have an update ready to go when the submission window re-opens in a couple weeks. Thanks, Mary. On Tue, Oct 22, 2013 at 6:50 AM, Brett Tate <brett@broadsoft.com> wrote: > Hi, > > The following are a few comments concerning > draft-ietf-sipcore-rfc4244bis-callflows-07. > > Thanks, > Brett > > ------- > > Global comment: "Max-Forward:" should be "Max-Forwards:". > > Section 3.2: > > 1) Figure 2: If not intentional, the ACK for the 302 is not shown. > > 2) F4: The Max-Forward (assuming Max-Forwards) should not be within the > response. > > 3) F4: To tag should be added for RFC 3261 compliance. > > 4) The F numbering should match the Figure 2. > > 5) Second F5: Based upon second F4, the "received=192.0.2.101" should be > "received=192.0.2.3". > > This email is intended solely for the person or entity to which it is > addressed and may contain confidential and/or privileged information. If > you are not the intended recipient and have received this email in error, > please notify BroadSoft, Inc. immediately by replying to this message, and > destroy all copies of this message, along with any attachment, prior to > reading, distributing or copying it. >