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

[Brett Tate <[e-mail]>]

Hi,

The following are some comments concerning
draft-ietf-insipid-session-id-12.

Thanks,
Brett

-------

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
Session-ID.

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 
<http://www.broadsoft.com/news/mobile-world-congress/>

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.