[Insipid] draft-ietf-insipid-session-id-12: comments

Brett Tate <brett@broadsoft.com> Tue, 20 January 2015 17:52 UTC

Return-Path: <brett@broadsoft.com>
X-Original-To: insipid@ietfa.amsl.com
Delivered-To: insipid@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com []) by ietfa.amsl.com (Postfix) with ESMTP id 87EA61B2AF8 for <insipid@ietfa.amsl.com>; Tue, 20 Jan 2015 09:52:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.08
X-Spam-Status: No, score=-0.08 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id pIUDEA9hjFL0 for <insipid@ietfa.amsl.com>; Tue, 20 Jan 2015 09:52:42 -0800 (PST)
Received: from mail-qc0-f180.google.com (mail-qc0-f180.google.com []) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BF7871B2AE2 for <insipid@ietf.org>; Tue, 20 Jan 2015 09:52:41 -0800 (PST)
Received: by mail-qc0-f180.google.com with SMTP id r5so25913359qcx.11 for <insipid@ietf.org>; Tue, 20 Jan 2015 09:52:41 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:mime-version:thread-index:date:message-id :subject:to:content-type; bh=ax9kHZQiUbR/DXSCLnSCkBiq0DRBamqy2stK21gUDic=; b=ERwFMvENWe/KuL0sklUf2S30DNxztd9NsOg6s9jZVMW4ntq+n4eyxrD4Y4ZBLuoXmk YF9hF8lXlb/wQG/VY+PDnhr7TsrH1qm04jXxczGSAah3T5T0G6hQlx9bTC7klliHeuYD 0TPVrMBvPxxg1UEeqor9jZvpyt2rOnm4Q7nP+rupucox/7Dwv2TQWn0NYHPpTZ/Q2dBj C+9KOUtSODargZ5Vp5Whj27leoA5aSN11u2L6u/bAglTIjJG2x3C4JJcyBFxXtPN76M0 jKVWO+0bFXFhGow8InLA2+N8TqRWRVer4siyYU4WA5DXndclY4V09G3TiN4yisFsmcRD 7hHA==
X-Gm-Message-State: ALoCoQkgBdceHWoFiKaRoF5Vh24GgNhUkKls5/7b6haO1P2hQo1IFIqq1im+EvuqipboOHEqXn43O0FhXkzrseJvIB48R54EmLNSI4SdZyxLh1ooPmYlAtM=
X-Received: by with SMTP id o8mr60471254qai.13.1421776361033; Tue, 20 Jan 2015 09:52:41 -0800 (PST)
From: Brett Tate <brett@broadsoft.com>
MIME-Version: 1.0
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AdA02dRJO0pfvq6/TbG0C3d9eOs5PA==
Date: Tue, 20 Jan 2015 12:52:40 -0500
Message-ID: <0b74a76d433bd9b9c05b68ebd6e33fdf@mail.gmail.com>
To: draft-ietf-insipid-session-id@tools.ietf.org, insipid@ietf.org
Content-Type: text/plain; charset="UTF-8"
Archived-At: <http://mailarchive.ietf.org/arch/msg/insipid/O4IQherWli44sdK2gCXG7xKZl6k>
Subject: [Insipid] draft-ietf-insipid-session-id-12: comments
X-BeenThere: insipid@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: SIP Session-ID discussion list <insipid.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/insipid>, <mailto:insipid-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/insipid/>
List-Post: <mailto:insipid@ietf.org>
List-Help: <mailto:insipid-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/insipid>, <mailto:insipid-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Jan 2015 17:52:44 -0000


The following are some comments concerning



Copyright: Replace 2014 with 2015.

Section 7 paragraph 6: Remove the extra period.  Potentially should reword
the sentence to avoid it sounding like the request constructs the

Section 9.1 F2, F3, and F5: Since UDP is the default transport, you might
want to change the top Via's transport to be UDP within F2, F3, and F5.

Section 9.1 F3: The Route should be removed; Record-Route URI must be
within <>.

Section 9.1 F5: The Route URI must be within <>.

Section 10 bullets 2 and 6: Bullet 2 isn't necessarily true since it can
occur within dialog after bullet 6.  However it raises some questions
concerning how the B2BUA should behave when swapping a connected party
over the same dialog.  For instance when the new endpoint and replaced
endpoint support different versions of Session-ID, does the B2BUA blindly
relay the new Session-ID (towards the remaining endpoint which supports
draft or only RFC 7329) or does it somehow apply section 10 rules?  For
instance consider RFC 3725 figure 13 where pre-paid user supports RFC
7329; called party supports draft and is actually the calling party; and
media server supports draft.  Message 6 could look like pre-paid user
supports draft; thus message 8 will contain a new Session-ID unless the
B2BUA is supposed to somehow apply section 10 to remedy the situation.


Meet with us at Mobile World Congress 2015 

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.