[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Sip] draft-kaplan-sip-session-id-00.txt
On Wed, 2008-12-03 at 23:43 -0500, Hadriel Kaplan wrote:
> >>
> >> |------ C
> >> |
> >> A ------ B
> >> |
> >> |------ D
> >>
>
> > -----Original Message-----
> > From: Paul Kyzivat [mailto:pkyzivat at cisco.com]
> > Sent: Wednesday, December 03, 2008 3:49 PM
> >
> > You mentioned something like "dialog-set". I'm not certain yet if "set"
> > is the proper term here. But assume for the moment that it is.
> >
> > Then what you really have is a "dialog-set-id" right? Not a session-id.
>
> I think very few people on this planet know what a SIP "dialog" is. :)
It's one of the few unambiguously defined things in SIP...
> But the word "Session" is a more common word for operators (even
> though its definition in SIP is far more ambiguous, IMO).
>
> For example, I think in your first 3PCC example (up top) most people
> really do expect that the same Session-ID be used for A-to-C. Whether
> it should be the same for B-D is what (IMO) is fine but not necessary,
> but that's just my opinion; and I bet plenty of operators would
> consider that the same "Session" too and be surprised if it wasn't.
"the same SFrom sip-bounces at ietf.org Fri Dec 5 08:39:46 2008
Return-Path: <sip-bounces at ietf.org>
X-Original-To: sip-archive at optimus.ietf.org
Delivered-To: ietfarch-sip-archive at core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
by core3.amsl.com (Postfix) with ESMTP id 3808B3A6C8E;
Fri, 5 Dec 2008 08:39:46 -0800 (PST)
X-Original-To: sip at core3.amsl.com
Delivered-To: sip at core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
by core3.amsl.com (Postfix) with ESMTP id 32D083A6C8F
for <sip at core3.amsl.com>; Fri, 5 Dec 2008 08:39:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.89
X-Spam-Level:
X-Spam-Status: No, score=-5.89 tagged_above=-999 required=5 tests=[AWL=-0.283,
BAYES_00=-2.599, DATE_IN_PAST_12_24=0.992, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
with ESMTP id cNB2rbBCQzfz for <sip at core3.amsl.com>;
Fri, 5 Dec 2008 08:39:43 -0800 (PST)
Received: from zrtps0kn.nortel.com (zrtps0kn.nortel.com [47.140.192.55])
by core3.amsl.com (Postfix) with ESMTP id 340E43A6C8D
for <sip at ietf.org>; Fri, 5 Dec 2008 08:39:43 -0800 (PST)
Received: from zrtphxs1.corp.nortel.com (zrtphxs1.corp.nortel.com
[47.140.202.46])
by zrtps0kn.nortel.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id
mB5GdX811012; Fri, 5 Dec 2008 16:39:34 GMT
Received: from [47.16.90.165] ([47.16.90.165]) by zrtphxs1.corp.nortel.com
with Microsoft SMTPSVC(6.0.3790.3959);
Fri, 5 Dec 2008 11:39:07 -0500
From: "Dale Worley" <dworley at nortel.com>
To: Hadriel Kaplan <HKaplan at acmepacket.com>
In-Reply-To: <E6C2E8958BA59A4FB960963D475F7AC3137BF57EA7 at mail>
References: <1228325321.3790.36.camel at victoria-pingtel-com.us.nortel.com>
<4936D015.8080006 at cisco.com>
<E6C2E8958BA59A4FB960963D475F7AC3137B9DCA2B at mail>
<4936F0A9.7010100 at cisco.com>
<E6C2E8958BA59A4FB960963D475F7AC3137BF57EA7 at mail>
Organization: Nortel Networks
Date: Thu, 04 Dec 2008 22:06:03 -0500
Message-Id: <1228446363.23019.10.camel at victoria-pingtel-com.us.nortel.com>
Mime-Version: 1.0
X-Mailer: Evolution 2.12.3 (2.12.3-5.fc8)
X-OriginalArrivalTime: 05 Dec 2008 16:39:07.0839 (UTC)
FILETIME=[FE324CF0:01C956F7]
Cc: SIP <sip at ietf.org>, Paul Kyzivat <pkyzivat at cisco.com>
Subject: Re: [Sip] draft-kaplan-sip-session-id-00.txt
X-BeenThere: sip at ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
<mailto:sip-request at ietf.org?subject=unsubscribe>
List-Post: <mailto:sip at ietf.org>
List-Help: <mailto:sip-request at ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
<mailto:sip-request at ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces at ietf.org
Errors-To: sip-bounces at ietf.org
On Wed, 2008-12-03 at 23:43 -0500, Hadriel Kaplan wrote:
> >>
> >> |------ C
> >> |
> >> A ------ B
> >> |
> >> |------ D
> >>
>
> > -----Original Message-----
> > From: Paul Kyzivat [mailto:pkyzivat at cisco.com]
> > Sent: Wednesday, December 03, 2008 3:49 PM
> >
> > You mentioned something like "dialog-set". I'm not certain yet if "set"
> > is the proper term here. But assume for the moment that it is.
> >
> > Then what you really have is a "dialog-set-id" right? Not a session-id.
>
> I think very few people on this planet know what a SIP "dialog" is. :)
It's one of the few unambiguously defined things in SIP...
> But the word "Session" is a more common word for operators (even
> though its definition in SIP is far more ambiguous, IMO).
>
> For example, I think in your first 3PCC example (up top) most people
> really do expect that the same Session-ID be used for A-to-C. Whether
> it should be the same for B-D is what (IMO) is fine but not necessary,
> but that's just my opinion; and I bet plenty of operators would
> consider that the same "Session" too and be surprised if it wasn't.
"the same Session-Iession-ID to be used for A-to-C" ... as is used for *what*?
Do you mean, "the same session-id to be used for the A-to-B and B-to-C
dialogs of the A-to-C session"?
Dale
_______________________________________________
Sip mailing list https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors at cs.columbia.edu for questions on current sip
Use sipping at ietf.org for new developments on the application of sip
D to be used for A-to-C" ... as is used for *what*?
Do you mean, "the same session-id to be used for the A-to-B and B-to-C
dialogs of the A-to-C session"?
Dale
_______________________________________________
Sip mailing list https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors at cs.columbia.edu for questions on current sip
Use sipping at ietf.org for new developments on the application of sip