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

Brett Tate <> Fri, 23 January 2015 10:32 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id A22B11A1AF6 for <>; Fri, 23 Jan 2015 02:32:08 -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 6uzLwEY3Om7L for <>; Fri, 23 Jan 2015 02:32:06 -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 A84F01A064C for <>; Fri, 23 Jan 2015 02:32:06 -0800 (PST)
Received: by with SMTP id l89so5389619qgf.3 for <>; Fri, 23 Jan 2015 02:32:06 -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=viqj6UbmfQ2wnVOVno4Muccj1VQ7bvTpsCdEhWH1u6Y=; b=IaWIIjIhbfdbaoJueDOTOjlMldM0elx+zG5GgDj/8VaHFMyBFkeoW+ZixOUgTqtRRw MjnHbElaNCNcjRka8K7pkct0F794AAjMtZ+fpQtnQmES3N9nNWTt0m6p8yLqzsZ84DwR GokxfH/V7+Ysexl4t6jOyXzOU/rO6YVaoNspF9h7R8TC93FIsSEUTKY4suqWq0qaS1kW rzNuaf4+E4wl+fyjM54u/3a/bFodnPhlfVFonIE7T9vpHobtM/OPBIGEtIgIMchpJ13M DvqPDILbb5J7ecDspXbu5+mvyw4cdipKxjRLzYY4R5uxN/Nxkm9CseTvn7nbe2JGQKUC kJrg==
X-Gm-Message-State: ALoCoQnCpVc3uJEaR2lkZCtDsF6/qmOrSgcSBt1iS4NL0pe0k9nucvGEDcAXDnBNRsflpptuWz7a5tZ2iA8o0neAiraA+FIx3+E7CpCoCnVh7nt408sqrrk=
X-Received: by with SMTP id s45mr11903084qgd.28.1422009125917; Fri, 23 Jan 2015 02:32:05 -0800 (PST)
From: Brett Tate <>
References: <em37ff103a-3044-4061-a066-ad64d62d4a32@sydney> <em2e612313-c475-4c80-a06b-11f48ddede49@sydney>
In-Reply-To: <em2e612313-c475-4c80-a06b-11f48ddede49@sydney>
MIME-Version: 1.0
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQKVoB+8sDMtN9VNPTvVWvz1Y8I0sptCqyXA
Date: Fri, 23 Jan 2015 05:32:05 -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 10:32:08 -0000


Thanks for the response.  Reply is inline.

> >>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.
> >
> >Unless there is a good reason to change these, I'd prefer
> >to leave them. UDP is still widely used, but TLS is also
> >extremely common. It's important that we don't have an error
> >here, of course. Any errors or just a preference for UDP.
> Actually, that would be "TLS".  Nonetheless, the question
> remains: is there a reason to change them to UDP?  If we do,
> I'd prefer to change all references to UDP just so it's all
> consistent.

I don't have a strong opinion on the topic.  The selected transport from
B2BUA to Bob violates the following SHOULD (assuming no reason to do

RFC 3263 section 4.1:

"Otherwise, if no transport protocol is specified, but the TARGET is a
numeric IP address, the client SHOULD use UDP for a SIP URI, and TCP
for a SIPS URI.  Similarly, if no transport protocol is specified,
and the TARGET is not numeric, but an explicit port is provided, the
client SHOULD use UDP for a SIP URI, and TCP for a SIPS URI.  This is
because UDP is the only mandatory transport in RFC 2543 [6], and thus
the only one guaranteed to be interoperable for a SIP URI.  It was
also specified as the default transport in RFC 2543 when no transport
was present in the SIP URI.  However, another transport, such as TCP,
MAY be used if the guidelines of SIP mandate it for this particular
request.  That is the case, for example, for requests that exceed the
path MTU."



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.