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

Brett Tate <> Fri, 23 January 2015 11:24 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id F12651A908A for <>; Fri, 23 Jan 2015 03:24:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.979
X-Spam-Status: No, score=-1.979 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id PaNST67KyW78 for <>; Fri, 23 Jan 2015 03:24:26 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 536121A8967 for <>; Fri, 23 Jan 2015 03:24:26 -0800 (PST)
Received: by with SMTP id q108so5524389qgd.0 for <>; Fri, 23 Jan 2015 03:24:25 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20130820; h=x-gm-message-state:from:references:in-reply-to:mime-version :thread-index:date:message-id:subject:to:content-type; bh=ktVpOYe7nLOEeck7iV1uqjMIsQy9XrZ8c4wl13L9irw=; b=RM2FVG39S8xQec+UuqQNdihZq109oCtDbWlj04++nUJ1ly6IiDizvZRhj69al62Cmh xqrKOCa8DXUr6TZ1ol0bbiypg17TMp3259KsUAq5IVSkAulSurFjb3CLYXxkb61wZxxu qN2l6wrKL2cCEk6uZhNE0+5Z3XlOgC1+Z+Zl1/6aVG7tLS91DW61V4RGXDJhFdzyP5Gr 906J2fNbkUmy1zTKLBZriC13NqXo4YJDacNZdZm7LpB/oVL30IySo3jr0eE340NHgDbW sq+rUdADhyX9WoXnq/J03+FxUjf6DewKb1H8JSRyWXJ6c94F6N7VWQmTCMkHJPbEMpqJ AgEw==
X-Gm-Message-State: ALoCoQkHQg23mGKFqqENVg81Z6v9nsINiUkhhyIaAEWQBUCDhh/k8ZIGP7aVDOWFC3pkeA2dLFjTEjDtoZE55z0vqatrwF9cyhBpWblhYA+JglRddJY7ogM=
X-Received: by with SMTP id s45mr12283330qgd.28.1422012265601; Fri, 23 Jan 2015 03:24:25 -0800 (PST)
From: Brett Tate <>
References: <> <em37ff103a-3044-4061-a066-ad64d62d4a32@sydney>
In-Reply-To: <em37ff103a-3044-4061-a066-ad64d62d4a32@sydney>
MIME-Version: 1.0
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQId/zpfrF0fowsm18gui7l+aIQgG5wx8YtA
Date: Fri, 23 Jan 2015 06:24:24 -0500
Message-ID: <>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <>
Subject: Re: [Insipid] draft-ietf-insipid-session-id-12: comments
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: SIP Session-ID discussion list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Fri, 23 Jan 2015 11:24:28 -0000


Thanks for the response; reply is inline.

> >Section 7 paragraph 6: Remove the extra period. Potentially
> >should reword the sentence to avoid it sounding like the
> >request constructs the Session-ID.
> How about this?
> "The Session-ID included in a CANCEL request MUST be
> identical to the Session-ID included in the corresponding

It sounds okay to me.

> >Section 10 bullets 2 and 6: Bullet 2 isn't necessarily
> >true since it can occur within dialog after bullet 6.
> This is just a statement of fact, no?  Shouldn't we keep
> it just to be clear and set a firm foundation?  And 6 is
> about the response, whereas 2 is about the request.

I was just highlighting that the bullet 2 is only potentially true since the
RFC 7329 device may send requests with the same exact Session-ID that the
draft compliant device sent within an originating INVITE.  Bullet 6 is
potentially adequate to help ensure that a draft compliant device won't
think that the remote party has become draft compliant mid dialog because of
bullet 2.

Concerning my adjusted RFC 3725 figure 13 example, there is currently
nothing to help the media server from incorrectly thinking that the remote
device is draft compliant since hit bullet 2.  A fix could be introduced by
allowing the B2BUA to indicate the non-compliance (by header or parameter)
to the media server.  However, introducing extra signaling complexity to
avoid the misinterpretation is potentially not worth it.



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.