
From ietf-secretariat-reply@ietf.org  Sun Nov  3 10:13:58 2013
Return-Path: <ietf-secretariat-reply@ietf.org>
X-Original-To: insipid@ietfa.amsl.com
Delivered-To: insipid@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7411311E80F8 for <insipid@ietfa.amsl.com>; Sun,  3 Nov 2013 10:13:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.494
X-Spam-Level: 
X-Spam-Status: No, score=-102.494 tagged_above=-999 required=5 tests=[AWL=0.106, BAYES_00=-2.599, 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 3PODjySbAgzP for <insipid@ietfa.amsl.com>; Sun,  3 Nov 2013 10:13:58 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 0AB5411E82CD for <insipid@ietf.org>; Sun,  3 Nov 2013 10:13:57 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
To: insipid@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 4.82
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20131103181357.1554.32711.idtracker@ietfa.amsl.com>
Date: Sun, 03 Nov 2013 10:13:57 -0800
From: IETF Secretariat <ietf-secretariat-reply@ietf.org>
X-Mailman-Approved-At: Sun, 03 Nov 2013 15:31:27 -0800
Subject: [Insipid] Milestones changed for insipid WG
X-BeenThere: insipid@ietf.org
X-Mailman-Version: 2.1.12
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: Sun, 03 Nov 2013 18:13:58 -0000

Changed milestone "Requirements and use cases for new identifier sent
to IESG (Informational)", set state to active from review, accepting
new milestone.

Changed milestone "Specification of the new identifier sent to the
IESG (Proposed Standard)", set state to active from review, accepting
new milestone.

Changed milestone "Requirements for marking SIP sessions for logging
to IESG (Informational)", set state to active from review, accepting
new milestone.

Changed milestone "Protocol for marking SIP sessions for logging to
IESG (Proposed Standard)", set state to active from review, accepting
new milestone.

URL: http://datatracker.ietf.org/wg/insipid/charter/

From keith.drage@alcatel-lucent.com  Mon Nov  4 10:26:54 2013
Return-Path: <keith.drage@alcatel-lucent.com>
X-Original-To: insipid@ietfa.amsl.com
Delivered-To: insipid@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C954F21E826D for <insipid@ietfa.amsl.com>; Mon,  4 Nov 2013 10:26:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.516
X-Spam-Level: 
X-Spam-Status: No, score=-110.516 tagged_above=-999 required=5 tests=[AWL=0.083, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, 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 6CfqLRJEnZFu for <insipid@ietfa.amsl.com>; Mon,  4 Nov 2013 10:26:48 -0800 (PST)
Received: from ihemail1.lucent.com (ihemail1.lucent.com [135.245.0.33]) by ietfa.amsl.com (Postfix) with ESMTP id 615EF21E818E for <insipid@ietf.org>; Mon,  4 Nov 2013 10:26:40 -0800 (PST)
Received: from fr711usmtp1.zeu.alcatel-lucent.com (h135-239-2-122.lucent.com [135.239.2.122]) by ihemail1.lucent.com (8.13.8/IER-o) with ESMTP id rA4IQcwj021198 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for <insipid@ietf.org>; Mon, 4 Nov 2013 12:26:39 -0600 (CST)
Received: from FR712WXCHHUB03.zeu.alcatel-lucent.com (fr712wxchhub03.zeu.alcatel-lucent.com [135.239.2.74]) by fr711usmtp1.zeu.alcatel-lucent.com (GMO) with ESMTP id rA4IQal8001386 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <insipid@ietf.org>; Mon, 4 Nov 2013 19:26:37 +0100
Received: from FR712WXCHMBA11.zeu.alcatel-lucent.com ([169.254.7.239]) by FR712WXCHHUB03.zeu.alcatel-lucent.com ([135.239.2.74]) with mapi id 14.02.0247.003; Mon, 4 Nov 2013 19:26:37 +0100
From: "DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com>
To: "insipid@ietf.org" <insipid@ietf.org>
Thread-Topic: Slides for today
Thread-Index: Ac7Zi2VL1YvhxLvdRvegf5kycxHcbQ==
Date: Mon, 4 Nov 2013 18:26:37 +0000
Message-ID: <949EF20990823C4C85C18D59AA11AD8B0C7E39@FR712WXCHMBA11.zeu.alcatel-lucent.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [135.239.27.38]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.33
Subject: [Insipid] Slides for today
X-BeenThere: insipid@ietf.org
X-Mailman-Version: 2.1.12
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: Mon, 04 Nov 2013 18:26:54 -0000

For those of you that have not yet sent them, can we have your presentation=
s for the meeting today as soon as possible.

Keith=

From internet-drafts@ietf.org  Mon Nov  4 11:59:10 2013
Return-Path: <internet-drafts@ietf.org>
X-Original-To: insipid@ietfa.amsl.com
Delivered-To: insipid@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E5C8B11E822A; Mon,  4 Nov 2013 11:59:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.569
X-Spam-Level: 
X-Spam-Status: No, score=-102.569 tagged_above=-999 required=5 tests=[AWL=0.031, BAYES_00=-2.599, 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 haosbeVW-pOP; Mon,  4 Nov 2013 11:59:10 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id EB56321E8229; Mon,  4 Nov 2013 11:59:06 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 4.82
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20131104195906.10152.15464.idtracker@ietfa.amsl.com>
Date: Mon, 04 Nov 2013 11:59:06 -0800
Cc: insipid@ietf.org
Subject: [Insipid] I-D Action: draft-ietf-insipid-session-id-reqts-09.txt
X-BeenThere: insipid@ietf.org
X-Mailman-Version: 2.1.12
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: Mon, 04 Nov 2013 19:59:11 -0000

A New Internet-Draft is available from the on-line Internet-Drafts director=
ies.
 This draft is a work item of the INtermediary-safe SIP session ID Working =
Group of the IETF.

	Title           : Requirements for an End-to-End Session Identification in=
 IP-Based Multimedia Communication Networks
	Author(s)       : Paul E. Jones
                          Gonzalo Salgueiro
                          James Polk
                          Laura Liess
                          Hadriel Kaplan
	Filename        : draft-ietf-insipid-session-id-reqts-09.txt
	Pages           : 12
	Date            : 2013-11-04

Abstract:
   This document specifies the requirements for an end-to-end session
   identifier in IP-based multimedia communication networks.  This
   identifier would enable endpoints, intermediate devices, and
   management and monitoring systems to identify a session end-to-end
   across multiple SIP devices, hops, and administrative domains.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-insipid-session-id-reqts

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-insipid-session-id-reqts-09

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-insipid-session-id-reqts-09


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From paulej@packetizer.com  Tue Nov  5 01:17:16 2013
Return-Path: <paulej@packetizer.com>
X-Original-To: insipid@ietfa.amsl.com
Delivered-To: insipid@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 58B9611E8264 for <insipid@ietfa.amsl.com>; Tue,  5 Nov 2013 01:17:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 CXgvjt7-vi8g for <insipid@ietfa.amsl.com>; Tue,  5 Nov 2013 01:17:11 -0800 (PST)
Received: from dublin.packetizer.com (dublin.packetizer.com [75.101.130.125]) by ietfa.amsl.com (Postfix) with ESMTP id 17F6F11E8255 for <insipid@ietf.org>; Tue,  5 Nov 2013 01:17:08 -0800 (PST)
Received: from [156.106.244.126] ([156.106.244.126]) (authenticated bits=0) by dublin.packetizer.com (8.14.5/8.14.5) with ESMTP id rA59GwVk015414 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 5 Nov 2013 04:16:59 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=packetizer.com; s=dublin; t=1383643021; bh=i8PLA/VOe2CbcGHdBm/9GdxkdTpPMAO3aKQWA3wqbVk=; h=From:To:Subject:Cc:Date:Content-Transfer-Encoding:Content-Type: Message-Id:Mime-Version:Reply-To; b=IQFSwsiTlJPsQbwOV3zKmvpEdn1F0ptuEkacMEZ9kjZXSydOCwod8j3Ftk3csy82H QRWxr8d3X+JwMWTERvaQme0HzIRnZgkB4a66wa2x+snNgR9xZ+sdOxQo8QFOecfNyN I94xj4ma7SPBUu6ARUDzLDcBIT6DbrhDWciU6hxY=
From: "Paul E. Jones" <paulej@packetizer.com>
To: insipid@ietf.org, "Elwyn Davies" <elwynd@dial.pipex.com>, "Vijay K. Gurbani" <vkg@bell-labs.com>
Date: Tue, 05 Nov 2013 09:17:07 +0000
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; format=flowed; charset=utf-8
Message-Id: <ema4a75357-6488-4d3b-bb4b-3b4e0bcd04b3@helsinki>
Mime-Version: 1.0
User-Agent: eM_Client/5.0.18661.0
Cc: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
Subject: [Insipid] Fw: I-D Action: draft-ietf-insipid-session-id-reqts-09.txt
X-BeenThere: insipid@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: "Paul E. Jones" <paulej@packetizer.com>
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, 05 Nov 2013 09:17:16 -0000

INSIPID WG and Reviewers,

Please note that I posted the below revised requirements document.  I=20
believe that all suggested changes are incorporated, with the exception=20
of proposed changes related to security considerations from Vijay.  The=20
WG had a few exchanges on the security consideration, but there wasn't=20
strong support for a more complete threat analysis in this document.

So, I would like to invite the the INSIPID WG members to review this=20
current draft and for the document reviewers to check to ensure that=20
their comments were addressed to their satisfaction.

I will not have time this week to make additional revisions, but I'll=20
make changes to the spec next week as required. If the text looks good,=20
please let us know so that we can move the text forward.

Paul

------ Forwarded Message ------
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
Cc: insipid@ietf.org
Sent: 11/4/2013 2:59:06 PM
Subject: [Insipid] I-D Action:=20
draft-ietf-insipid-session-id-reqts-09.txt


A New Internet-Draft is available from the on-line Internet-Drafts=20
directories.
  This draft is a work item of the INtermediary-safe SIP session ID=20
Working Group of the IETF.

  Title : Requirements for an End-to-End Session Identification in=20
IP-Based Multimedia Communication Networks
  Author(s) : Paul E. Jones
                           Gonzalo Salgueiro
                           James Polk
                           Laura Liess
                           Hadriel Kaplan
  Filename : draft-ietf-insipid-session-id-reqts-09.txt
  Pages : 12
  Date : 2013-11-04

Abstract:
    This document specifies the requirements for an end-to-end session
    identifier in IP-based multimedia communication networks. This
    identifier would enable endpoints, intermediate devices, and
    management and monitoring systems to identify a session end-to-end
    across multiple SIP devices, hops, and administrative domains.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-insipid-session-id-reqts

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-insipid-session-id-reqts-09

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-insipid-session-id-reqts-09


Please note that it may take a couple of minutes from the time of=20
submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

_______________________________________________
insipid mailing list
insipid@ietf.org
https://www.ietf.org/mailman/listinfo/insipid


From brett@broadsoft.com  Tue Nov  5 08:13:19 2013
Return-Path: <brett@broadsoft.com>
X-Original-To: insipid@ietfa.amsl.com
Delivered-To: insipid@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DD4F721E8264 for <insipid@ietfa.amsl.com>; Tue,  5 Nov 2013 08:13:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.589
X-Spam-Level: 
X-Spam-Status: No, score=-1.589 tagged_above=-999 required=5 tests=[AWL=-1.010, BAYES_00=-2.599, LOCALPART_IN_SUBJECT=2.02]
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 iARGNEkxURmb for <insipid@ietfa.amsl.com>; Tue,  5 Nov 2013 08:13:13 -0800 (PST)
Received: from smtpout01.partnerhosted.com (smtpout01.partnerhosted.com [173.225.22.21]) by ietfa.amsl.com (Postfix) with ESMTP id 87C0921E8255 for <insipid@ietf.org>; Tue,  5 Nov 2013 08:13:13 -0800 (PST)
Received: from CASUMHUB05.citservers.local (172.16.98.229) by Xedge02.citservers.local (172.16.98.248) with Microsoft SMTP Server (TLS) id 14.2.247.3; Tue, 5 Nov 2013 08:14:40 -0800
Received: from MBX08.citservers.local ([fe80::2564:652:8dc8:caae]) by casumhub05.citservers.local ([::1]) with mapi id 14.02.0247.003; Tue, 5 Nov 2013 08:14:39 -0800
From: Brett Tate <brett@broadsoft.com>
To: "draft-kaplan-insipid-session-id@tools.ietf.org" <draft-kaplan-insipid-session-id@tools.ietf.org>, "insipid@ietf.org" <insipid@ietf.org>
Thread-Topic: draft-kaplan-insipid-session-id: parameters and session-id
Thread-Index: Ac7aQevgzPLp21YkTEabLapkDDfqvA==
Date: Tue, 5 Nov 2013 16:14:39 +0000
Message-ID: <576A8B541C219D4E9CEB1DF8C19C7B881A06791D@MBX08.citservers.local>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [172.16.98.77]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: [Insipid] draft-kaplan-insipid-session-id: parameters and session-id
X-BeenThere: insipid@ietf.org
X-Mailman-Version: 2.1.12
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, 05 Nov 2013 16:13:19 -0000

Hi,

Concerning the topic of backward compatibility with draft-kaplan-insipid-se=
ssion-id, I'm not sure that I understand sections 4.2 and 4.3 of draft-kapl=
an-insipid-session-id-03 concerning parameters and Session-ID header modifi=
cations.

Section 4.2 indicates:
"The UAC MUST re-use the same Session-ID value for in-dialog messages
 as that of the original dialog-creating request".

Section 4.3 indicates:
"A UAS compliant with this document MUST copy a received Session-ID
 header field in a request, into responses and subsequent upstream
 requests sent within the dialog."

What should the generator of the Session-ID (from section 4.2 perspective) =
do if receives mid-dialog Session-ID header modification within a request?

1) Follow section 4.2 MUST.
2) Follow section 4.3 MUST.
3) It is abnormal situation; thus it can do whatever it wants.

What if there is only a parameter modification: added, removed, or value ch=
ange?

What should the generator of the Session-ID (from section 4.2 perspective) =
do if receives Session-ID header modification within a response?

Concerning the section 4.2 and 4.3 snippets, my understanding is that the M=
UST includes parameters (instead of just Session-ID's sess-id).  Is my inte=
rpretation correct?  I thought that I'd ask to ensure that I'm not misinter=
preting the use of "value" and "field".

Thanks,
Brett

This email is intended solely for the person or entity to which it is addre=
ssed and may contain confidential and/or privileged information. If you are=
 not the intended recipient and have received this email in error, please n=
otify BroadSoft, Inc. immediately by replying to this message, and destroy =
all copies of this message, along with any attachment, prior to reading, di=
stributing or copying it.

From pkyzivat@alum.mit.edu  Tue Nov  5 13:04:02 2013
Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: insipid@ietfa.amsl.com
Delivered-To: insipid@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7A1FE11E8110 for <insipid@ietfa.amsl.com>; Tue,  5 Nov 2013 13:04:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.437
X-Spam-Level: 
X-Spam-Status: No, score=-0.437 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_NET=0.611,  RDNS_NONE=0.1]
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 TrvYQ3OVRcMp for <insipid@ietfa.amsl.com>; Tue,  5 Nov 2013 13:03:57 -0800 (PST)
Received: from qmta13.westchester.pa.mail.comcast.net (qmta13.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:44:76:96:59:243]) by ietfa.amsl.com (Postfix) with ESMTP id 8171211E8219 for <insipid@ietf.org>; Tue,  5 Nov 2013 13:03:52 -0800 (PST)
Received: from omta07.westchester.pa.mail.comcast.net ([76.96.62.59]) by qmta13.westchester.pa.mail.comcast.net with comcast id ltnG1m0031GhbT85Dx3suV; Tue, 05 Nov 2013 21:03:52 +0000
Received: from dhcp-a502.meeting.ietf.org ([31.133.165.2]) by omta07.westchester.pa.mail.comcast.net with comcast id lx1k1m00203RZsX3Tx1miM; Tue, 05 Nov 2013 21:01:50 +0000
Message-ID: <52795CBC.2070505@alum.mit.edu>
Date: Tue, 05 Nov 2013 13:01:48 -0800
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.1.0
MIME-Version: 1.0
To: insipid@ietf.org
References: <576A8B541C219D4E9CEB1DF8C19C7B881A06791D@MBX08.citservers.local>
In-Reply-To: <576A8B541C219D4E9CEB1DF8C19C7B881A06791D@MBX08.citservers.local>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1383685432; bh=5Tp509pCnBHOp5W5ocrbvp7kTn62y2NBAHwb+G48sFg=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=dGqtju1EnDHcn/wbo7cOl3pWdQbVuz6GxJ/rS/PmQWBVH8sJMCmZ39IAKhzMIUI56 z9gGOFvNlX/EDyYpg7ii8npyOywaHlEqvZhuLnxBKMV6R1UGefdY9CLEPr/jIehkql lRt/DD7Qy6t+NpNH/HLCtDvQqOTtPXNtLSshk72DIwRD/NacMimHKSHe2lUaGZIxda /zFsTu1YSj9awfr6OXpgfUW7zz2FuUWDxu3Zu1A9W669S78aerU87y5Vf8ohrRvaf+ iKLCWtcGs5Gs4mqqF1B/CdfyyTrSPCFewAL3bA2j6HfVrL9CTesZUrr/e2MHx6Y9wn X4hnvPG5tdaMQ==
Subject: Re: [Insipid] draft-kaplan-insipid-session-id: parameters and session-id
X-BeenThere: insipid@ietf.org
X-Mailman-Version: 2.1.12
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, 05 Nov 2013 21:04:02 -0000

Brett,

Since the kaplan draft is effectively historical, intended to document 
something that has already been implemented, its not evident to me that 
asking clarifying questions about it is useful. If you have those 
questions, then the implementers of it must have had them too, or failed 
to realize the ambiguity.

I think the only things it is helpful to consider are:
- what behaviors would be plausibly compliant with kaplan?
- what do actual known implementations of kaplan actually do?

	Thanks,
	Paul

On 11/5/13 8:14 AM, Brett Tate wrote:
> Hi,
>
> Concerning the topic of backward compatibility with draft-kaplan-insipid-session-id, I'm not sure that I understand sections 4.2 and 4.3 of draft-kaplan-insipid-session-id-03 concerning parameters and Session-ID header modifications.
>
> Section 4.2 indicates:
> "The UAC MUST re-use the same Session-ID value for in-dialog messages
>   as that of the original dialog-creating request".
>
> Section 4.3 indicates:
> "A UAS compliant with this document MUST copy a received Session-ID
>   header field in a request, into responses and subsequent upstream
>   requests sent within the dialog."
>
> What should the generator of the Session-ID (from section 4.2 perspective) do if receives mid-dialog Session-ID header modification within a request?
>
> 1) Follow section 4.2 MUST.
> 2) Follow section 4.3 MUST.
> 3) It is abnormal situation; thus it can do whatever it wants.
>
> What if there is only a parameter modification: added, removed, or value change?
>
> What should the generator of the Session-ID (from section 4.2 perspective) do if receives Session-ID header modification within a response?
>
> Concerning the section 4.2 and 4.3 snippets, my understanding is that the MUST includes parameters (instead of just Session-ID's sess-id).  Is my interpretation correct?  I thought that I'd ask to ensure that I'm not misinterpreting the use of "value" and "field".
>
> Thanks,
> Brett
>
> 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.
> _______________________________________________
> insipid mailing list
> insipid@ietf.org
> https://www.ietf.org/mailman/listinfo/insipid
>


From keith.drage@alcatel-lucent.com  Tue Nov  5 13:14:53 2013
Return-Path: <keith.drage@alcatel-lucent.com>
X-Original-To: insipid@ietfa.amsl.com
Delivered-To: insipid@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 409F921E8093 for <insipid@ietfa.amsl.com>; Tue,  5 Nov 2013 13:14:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.527
X-Spam-Level: 
X-Spam-Status: No, score=-110.527 tagged_above=-999 required=5 tests=[AWL=0.072, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, 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 mGORGtlq1Z-Y for <insipid@ietfa.amsl.com>; Tue,  5 Nov 2013 13:14:47 -0800 (PST)
Received: from ihemail3.lucent.com (ihemail3.lucent.com [135.245.0.37]) by ietfa.amsl.com (Postfix) with ESMTP id B9E3A11E8175 for <insipid@ietf.org>; Tue,  5 Nov 2013 13:14:47 -0800 (PST)
Received: from fr711usmtp1.zeu.alcatel-lucent.com (h135-239-2-122.lucent.com [135.239.2.122]) by ihemail3.lucent.com (8.13.8/IER-o) with ESMTP id rA5LEinB024514 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Tue, 5 Nov 2013 15:14:46 -0600 (CST)
Received: from FR711WXCHHUB01.zeu.alcatel-lucent.com (fr711wxchhub01.zeu.alcatel-lucent.com [135.239.2.111]) by fr711usmtp1.zeu.alcatel-lucent.com (GMO) with ESMTP id rA5LEgO0030922 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 5 Nov 2013 22:14:43 +0100
Received: from FR712WXCHMBA11.zeu.alcatel-lucent.com ([169.254.7.239]) by FR711WXCHHUB01.zeu.alcatel-lucent.com ([135.239.2.111]) with mapi id 14.02.0247.003; Tue, 5 Nov 2013 22:14:43 +0100
From: "DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>, "insipid@ietf.org" <insipid@ietf.org>
Thread-Topic: [Insipid] draft-kaplan-insipid-session-id: parameters and session-id
Thread-Index: AQHO2mqYJyuA+F/82kefeu6ZuEGgnJoXItvA
Date: Tue, 5 Nov 2013 21:14:42 +0000
Message-ID: <949EF20990823C4C85C18D59AA11AD8B0C94EF@FR712WXCHMBA11.zeu.alcatel-lucent.com>
References: <576A8B541C219D4E9CEB1DF8C19C7B881A06791D@MBX08.citservers.local> <52795CBC.2070505@alum.mit.edu>
In-Reply-To: <52795CBC.2070505@alum.mit.edu>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [135.239.27.38]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.37
Subject: Re: [Insipid] draft-kaplan-insipid-session-id: parameters and	session-id
X-BeenThere: insipid@ietf.org
X-Mailman-Version: 2.1.12
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, 05 Nov 2013 21:14:53 -0000

Personally I'd probably follow 4.3, but if both sides are operating correct=
ly, there should not be a conflict.

To add to Paul's discussion points, it is also a question of whether any am=
biguity causes misoperation.

Keith=20

> -----Original Message-----
> From: insipid-bounces@ietf.org=20
> [mailto:insipid-bounces@ietf.org] On Behalf Of Paul Kyzivat
> Sent: 05 November 2013 21:02
> To: insipid@ietf.org
> Subject: Re: [Insipid] draft-kaplan-insipid-session-id:=20
> parameters and session-id
>=20
> Brett,
>=20
> Since the kaplan draft is effectively historical, intended to=20
> document something that has already been implemented, its not=20
> evident to me that asking clarifying questions about it is=20
> useful. If you have those questions, then the implementers of=20
> it must have had them too, or failed to realize the ambiguity.
>=20
> I think the only things it is helpful to consider are:
> - what behaviors would be plausibly compliant with kaplan?
> - what do actual known implementations of kaplan actually do?
>=20
> 	Thanks,
> 	Paul
>=20
> On 11/5/13 8:14 AM, Brett Tate wrote:
> > Hi,
> >
> > Concerning the topic of backward compatibility with=20
> draft-kaplan-insipid-session-id, I'm not sure that I=20
> understand sections 4.2 and 4.3 of=20
> draft-kaplan-insipid-session-id-03 concerning parameters and=20
> Session-ID header modifications.
> >
> > Section 4.2 indicates:
> > "The UAC MUST re-use the same Session-ID value for=20
> in-dialog messages
> >   as that of the original dialog-creating request".
> >
> > Section 4.3 indicates:
> > "A UAS compliant with this document MUST copy a received Session-ID
> >   header field in a request, into responses and subsequent upstream
> >   requests sent within the dialog."
> >
> > What should the generator of the Session-ID (from section=20
> 4.2 perspective) do if receives mid-dialog Session-ID header=20
> modification within a request?
> >
> > 1) Follow section 4.2 MUST.
> > 2) Follow section 4.3 MUST.
> > 3) It is abnormal situation; thus it can do whatever it wants.
> >
> > What if there is only a parameter modification: added,=20
> removed, or value change?
> >
> > What should the generator of the Session-ID (from section=20
> 4.2 perspective) do if receives Session-ID header=20
> modification within a response?
> >
> > Concerning the section 4.2 and 4.3 snippets, my=20
> understanding is that the MUST includes parameters (instead=20
> of just Session-ID's sess-id).  Is my interpretation correct?=20
>  I thought that I'd ask to ensure that I'm not=20
> misinterpreting the use of "value" and "field".
> >
> > Thanks,
> > Brett
> >
> > This email is intended solely for the person or entity to=20
> which it is addressed and may contain confidential and/or=20
> privileged information. If you are not the intended recipient=20
> and have received this email in error, please notify=20
> BroadSoft, Inc. immediately by replying to this message, and=20
> destroy all copies of this message, along with any=20
> attachment, prior to reading, distributing or copying it.
> > _______________________________________________
> > insipid mailing list
> > insipid@ietf.org
> > https://www.ietf.org/mailman/listinfo/insipid
> >
>=20
> _______________________________________________
> insipid mailing list
> insipid@ietf.org
> https://www.ietf.org/mailman/listinfo/insipid
> =

From vkg@bell-labs.com  Tue Nov  5 17:17:42 2013
Return-Path: <vkg@bell-labs.com>
X-Original-To: insipid@ietfa.amsl.com
Delivered-To: insipid@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0121121F9CAC for <insipid@ietfa.amsl.com>; Tue,  5 Nov 2013 17:17:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level: 
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, 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 3L18j93aHBVy for <insipid@ietfa.amsl.com>; Tue,  5 Nov 2013 17:17:37 -0800 (PST)
Received: from ihemail3.lucent.com (ihemail3.lucent.com [135.245.0.37]) by ietfa.amsl.com (Postfix) with ESMTP id 0D25E11E81F9 for <insipid@ietf.org>; Tue,  5 Nov 2013 17:17:36 -0800 (PST)
Received: from usnavsmail4.ndc.alcatel-lucent.com (usnavsmail4.ndc.alcatel-lucent.com [135.3.39.12]) by ihemail3.lucent.com (8.13.8/IER-o) with ESMTP id rA61HUXQ014279 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Tue, 5 Nov 2013 19:17:31 -0600 (CST)
Received: from umail.lucent.com (umail.ndc.lucent.com [135.3.40.61]) by usnavsmail4.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id rA61HUch010794 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 5 Nov 2013 19:17:30 -0600
Received: from shoonya.ih.lucent.com (vkg.lra.lucent.com [135.244.18.43]) by umail.lucent.com (8.13.8/TPES) with ESMTP id rA61HS5j023807; Tue, 5 Nov 2013 19:17:29 -0600 (CST)
Message-ID: <5279989F.3000800@bell-labs.com>
Date: Tue, 05 Nov 2013 19:17:19 -0600
From: "Vijay K. Gurbani" <vkg@bell-labs.com>
Organization: Bell Laboratories, Alcatel-Lucent
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130805 Thunderbird/17.0.8
MIME-Version: 1.0
To: "Paul E. Jones" <paulej@packetizer.com>
References: <ema4a75357-6488-4d3b-bb4b-3b4e0bcd04b3@helsinki>
In-Reply-To: <ema4a75357-6488-4d3b-bb4b-3b4e0bcd04b3@helsinki>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.37
X-Scanned-By: MIMEDefang 2.64 on 135.3.39.12
X-Mailman-Approved-At: Tue, 05 Nov 2013 17:23:12 -0800
Cc: Elwyn Davies <elwynd@dial.pipex.com>, insipid@ietf.org, Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
Subject: Re: [Insipid] Fw: I-D Action: draft-ietf-insipid-session-id-reqts-09.txt
X-BeenThere: insipid@ietf.org
X-Mailman-Version: 2.1.12
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: Wed, 06 Nov 2013 01:17:42 -0000

On 11/05/2013 03:17 AM, Paul E. Jones wrote:
> INSIPID WG and Reviewers,
>
> Please note that I posted the below revised requirements document.  I
> believe that all suggested changes are incorporated, with the exception
> of proposed changes related to security considerations from Vijay.  The
> WG had a few exchanges on the security consideration, but there wasn't
> strong support for a more complete threat analysis in this document.

Paul: No worries.  Thanks for entertaining me.  I have no further
comments on the draft.

Thanks,

- vijay
-- 
Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent
1960 Lucent Lane, Rm. 9C-533, Naperville, Illinois 60563 (USA)
Email: vkg@{bell-labs.com,acm.org} / vijay.gurbani@alcatel-lucent.com
Web: http://ect.bell-labs.com/who/vkg/  | Calendar: http://goo.gl/x3Ogq

From brett@broadsoft.com  Wed Nov  6 03:45:19 2013
Return-Path: <brett@broadsoft.com>
X-Original-To: insipid@ietfa.amsl.com
Delivered-To: insipid@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3917C21E809C for <insipid@ietfa.amsl.com>; Wed,  6 Nov 2013 03:45:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.521
X-Spam-Level: 
X-Spam-Status: No, score=-2.521 tagged_above=-999 required=5 tests=[AWL=0.078,  BAYES_00=-2.599]
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 H-ZO5KC3sCNv for <insipid@ietfa.amsl.com>; Wed,  6 Nov 2013 03:45:14 -0800 (PST)
Received: from smtpout01.partnerhosted.com (smtpout01.partnerhosted.com [173.225.22.21]) by ietfa.amsl.com (Postfix) with ESMTP id E40D721E8088 for <insipid@ietf.org>; Wed,  6 Nov 2013 03:45:13 -0800 (PST)
Received: from CASUMHUB04.citservers.local (172.16.98.225) by Xedge02.citservers.local (172.16.98.248) with Microsoft SMTP Server (TLS) id 14.2.247.3; Wed, 6 Nov 2013 03:46:40 -0800
Received: from MBX08.citservers.local ([fe80::2564:652:8dc8:caae]) by CASUMHUB04.citservers.local ([::1]) with mapi id 14.02.0247.003; Wed, 6 Nov 2013 03:44:46 -0800
From: Brett Tate <brett@broadsoft.com>
To: "DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com>, Paul Kyzivat <pkyzivat@alum.mit.edu>, "insipid@ietf.org" <insipid@ietf.org>
Thread-Topic: [Insipid] draft-kaplan-insipid-session-id: parameters	and session-id
Thread-Index: AQHO2mqYJyuA+F/82kefeu6ZuEGgnJoXItvAgADVNGA=
Date: Wed, 6 Nov 2013 11:44:45 +0000
Message-ID: <576A8B541C219D4E9CEB1DF8C19C7B881A067B8D@MBX08.citservers.local>
References: <576A8B541C219D4E9CEB1DF8C19C7B881A06791D@MBX08.citservers.local> <52795CBC.2070505@alum.mit.edu> <949EF20990823C4C85C18D59AA11AD8B0C94EF@FR712WXCHMBA11.zeu.alcatel-lucent.com>
In-Reply-To: <949EF20990823C4C85C18D59AA11AD8B0C94EF@FR712WXCHMBA11.zeu.alcatel-lucent.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [172.16.98.77]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [Insipid] draft-kaplan-insipid-session-id: parameters	and session-id
X-BeenThere: insipid@ietf.org
X-Mailman-Version: 2.1.12
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: Wed, 06 Nov 2013 11:45:19 -0000

Hi,

Thanks for the responses.  I'm asking the questions to better understand an=
d evaluate draft-ietf-insipid-session-id from a backward compatibility pers=
pective with draft-kaplan-insipid-session-id.  I look forward to the next v=
ersion of draft-ietf-insipid-session-id since it might provide answers to m=
y questions (at least from insipid perspective interacting with a draft-kap=
lan-insipid-session-id device).

One of the call flows of interest is associated with B2BUA acting as 3PCC s=
imulating call waiting type interaction (similar to RFC 3725 figure 13 if a=
ssume message 6 is a re-INVITE) using re-INVITE (from B2BUA) to reconnect a=
n insipid device (X) back and forth between connections with insipid device=
 (I) and kaplan device (K).  My current understanding is that X theoretical=
ly might change remote value and include parameter changes (new, dropped, o=
r modified).  Thus from a B2BUA perspective, I'd need to know how draft-iet=
f-insipid-session-id proposes the B2BUA behave to allow backward compatibil=
ity with K.  For instance, should it send the completely new Session-ID hea=
der (i.e. new sess-id and parameters) to K or continue to send the prior Se=
ssion-ID header (such as the Session-ID used when dialog created)?  Should =
prior knowledge of K's non support of draft-ietf-insipid-session-id cause t=
he B2BUA to not include a draft-ietf-insipid-session-id Session-ID within t=
he re-invite sent to X?

Thanks,
Brett

> -----Original Message-----
> From: insipid-bounces@ietf.org [mailto:insipid-bounces@ietf.org] On
> Behalf Of DRAGE, Keith (Keith)
> Sent: Tuesday, November 05, 2013 4:15 PM
> To: Paul Kyzivat; insipid@ietf.org
> Subject: Re: [Insipid] draft-kaplan-insipid-session-id: parameters and
> session-id
>=20
> Personally I'd probably follow 4.3, but if both sides are operating
> correctly, there should not be a conflict.
>=20
> To add to Paul's discussion points, it is also a question of whether
> any ambiguity causes misoperation.
>=20
> Keith
>=20
> > -----Original Message-----
> > From: insipid-bounces@ietf.org
> > [mailto:insipid-bounces@ietf.org] On Behalf Of Paul Kyzivat
> > Sent: 05 November 2013 21:02
> > To: insipid@ietf.org
> > Subject: Re: [Insipid] draft-kaplan-insipid-session-id:
> > parameters and session-id
> >
> > Brett,
> >
> > Since the kaplan draft is effectively historical, intended to
> > document something that has already been implemented, its not
> > evident to me that asking clarifying questions about it is
> > useful. If you have those questions, then the implementers of
> > it must have had them too, or failed to realize the ambiguity.
> >
> > I think the only things it is helpful to consider are:
> > - what behaviors would be plausibly compliant with kaplan?
> > - what do actual known implementations of kaplan actually do?
> >
> > 	Thanks,
> > 	Paul
> >
> > On 11/5/13 8:14 AM, Brett Tate wrote:
> > > Hi,
> > >
> > > Concerning the topic of backward compatibility with
> > draft-kaplan-insipid-session-id, I'm not sure that I
> > understand sections 4.2 and 4.3 of
> > draft-kaplan-insipid-session-id-03 concerning parameters and
> > Session-ID header modifications.
> > >
> > > Section 4.2 indicates:
> > > "The UAC MUST re-use the same Session-ID value for
> > in-dialog messages
> > >   as that of the original dialog-creating request".
> > >
> > > Section 4.3 indicates:
> > > "A UAS compliant with this document MUST copy a received Session-ID
> > >   header field in a request, into responses and subsequent upstream
> > >   requests sent within the dialog."
> > >
> > > What should the generator of the Session-ID (from section
> > 4.2 perspective) do if receives mid-dialog Session-ID header
> > modification within a request?
> > >
> > > 1) Follow section 4.2 MUST.
> > > 2) Follow section 4.3 MUST.
> > > 3) It is abnormal situation; thus it can do whatever it wants.
> > >
> > > What if there is only a parameter modification: added,
> > removed, or value change?
> > >
> > > What should the generator of the Session-ID (from section
> > 4.2 perspective) do if receives Session-ID header
> > modification within a response?
> > >
> > > Concerning the section 4.2 and 4.3 snippets, my
> > understanding is that the MUST includes parameters (instead
> > of just Session-ID's sess-id).  Is my interpretation correct?
> >  I thought that I'd ask to ensure that I'm not
> > misinterpreting the use of "value" and "field".
> > >
> > > Thanks,
> > > Brett

