Robert Sparks | 3 Dec 2002 16:19

SIPIT 12 registration is open

The 12th SIPit will be hosted by Hotsip in Stockholm
February 24-28, 2003.

Please see
http://www.hotsip.com/sipit12/
for details and registration.

There were several SIMPLE implementations at the
last SIPIT. I expect more at this one (drop me
a note if you're planning to attend). We will have
a multiparty session testing SIMPLE interoperability
at this event.

Thanks,

RjS
Jonathan Rosenberg | 3 Dec 2002 21:22

Updated presence specs

Folks,

I've just submitted an update to all three core presence specs 
(presence, watcherinfo package, watcherinfo format) based on comments 
received during last call, including those from our AD. Until they 
appear in the archives, you can pick them up at:

http://www.jdrosen.net/papers/draft-ietf-simple-presence-08.txt
http://www.jdrosen.net/papers/draft-ietf-simple-winfo-package-03.txt
http://www.jdrosen.net/papers/draft-ietf-simple-winfo-format-03.txt

THe changes are mostly minor. Below you will find a summary.

PRESENCE
--------
* reduced the author list to one, as I have been the primary author
and editor for some time. This was at the request of Patrik, and is
consistent with RFC-editor policy on author lists. The remainder of
the author list was moved to a contributor section.

* Section 4, overview of operation, reported that a SUBSCRIBE with
Expires: 0, used for fetch, was identical to processing of a SUBSCRIBE
with a non-zero Expires, in that both result in an immediate
NOTIFY. This isn't true. An immediate NOTIFY is only sent, in all
cases, when the SUBSCRIBE is either pending or authorized. Clarified
that.

* Reworked the section on replay prevention. Added a few paragraphs
describing why replay was bad. Remvoed the text which talked about
including Call-ID, CSeq and Date headers in the signature; that
(Continue reading)

Jonathan Rosenberg | 6 Dec 2002 08:57

minor updates to presence spec and watcherinfo spec

Folks,

I've just submitted another update to the presence spec and the 
watcherinfo changes. The updates are minor and address further iesg 
comments. Until they appear in the archives, you can grab them from:

http://www.jdrosen.net/papers/draft-ietf-simple-winfo-package-04.txt
http://www.jdrosen.net/papers/draft-ietf-simple-presence-09.txt

The changes are summarized below.

PRESENCE
--------
* in the pres URI discussion, it says that SIP URI is preferred when its
known. Fixed to say SIP or SIPS URI, instead of just SIP URI.

* removed references to p-header network asserted ID drafts as a means
to establish identity. Text now reads:

In inter-domain scenarios, establishing an authenticated identity of
the subscriber is harder. It is anticipated that authentication will
often be established through transitive trust. SIP mechanisms
for network asserted identity can be applied to establish the identity
of the subscriber \citenonnorm{draft-ietf-sip-identity}.

* removed text which said that you can send notifications faster than
once every 5 seconds if an extension explicitly says its OK.

* explicit mention of rfc2779 as an influence on security
considerations.
(Continue reading)

Sudipta Ghosh | 6 Dec 2002 11:29

Event

Hi,
When IM Client is sending a SUBSCRIPTION request( to a offline user )
for presence notification to proxy,proxy sends response with 200 OK but
adds a event header.

Whats the meaning of it.

In REGISTER request there is also a Event header.
I am sending the packets.(got from MSN Messenger communication service)

SUBSCRIBE sip:sudipta <at> 10.140.13.149 SIP/2.0
Via: SIP/2.0/TCP 10.140.13.178:9172
From: "i" <sip:i <at> 10.140.13.149>;tag=5a9e885b-5af7-45b4-ad41-33eb48ae6a99

To: <sip:sudipta <at> 10.140.13.149>
Call-ID: 382d3998-db28-409d-b692-fedf56a685fe <at> 10.140.13.178
CSeq: 1 SUBSCRIBE
Contact: <sip:10.140.13.178:9172;transport=tcp>
User-Agent: Windows RTC/1.0
Expires: 1800
Content-Length: 0

SIP/2.0 200 OK
Via: SIP/2.0/TCP 10.140.13.178:9172;received-port=5060
To: sip:sudipta <at> 10.140.13.149;tag=UKXBY32U8GYZBRWM
CSeq: 1 SUBSCRIBE
From: "i" <sip:i <at> 10.140.13.149>;tag=5a9e885b-5af7-45b4-ad41-33eb48ae6a99

Call-ID: 382d3998-db28-409d-b692-fedf56a685fe <at> 10.140.13.178
Event: presence
(Continue reading)

Sudipta Ghosh | 6 Dec 2002 15:59

info

hi,
is there any free/demo sip/simple server available so we can login
through MSN Messenger
communication server.
sudipta

--
***********************************************
System Executive
Scicom Infotech Pvt. Ltd. (Scicom)
A - 67, Sector - 57
Noida - 201 301
UP
**********************************************
Jonathan Rosenberg | 6 Dec 2002 17:11

Re: Event

answers inline.

Sudipta Ghosh wrote:
> Hi,
> When IM Client is sending a SUBSCRIPTION request( to a offline user )

The request method is SUBSCRIBE, not SUBSCRIPTION.

> for presence notification to proxy,proxy sends response with 200 OK but
> adds a event header.

The SUBSCRIBE request contains the Event header. It is not placed in the 
200 OK response. It is, however, placed in the NOTIFY request generated 
by the presence server.

> 
> Whats the meaning of it.

SIP has a general events framework (RFC 3265). A particular resource, 
such as sip:jdrosen <at> dynamicsoft.com, can support multiple types of 
events, including presence, message waiting indicators, dialog events, 
etc. The Event header disambiguates the event types being requested of 
the resource. See RFC 3265 for a complete discussion.

> 
> In REGISTER request there is also a Event header.

No, there is no Event header in REGISTER.

> I am sending the packets.(got from MSN Messenger communication service)
(Continue reading)

Cullen Jennings | 8 Dec 2002 18:43
Picon
Favicon
Gravatar

RE: I-D ACTION:draft-ietf-simple-presence-08.txt


I'm confused - is it version 8 or 9?  all I can find is 
http://www.ietf.org/internet-drafts/draft-ietf-simple-presence-09.txt

> -----Original Message-----
> From: scoya <at> cnri.reston.va.us [mailto:scoya <at> cnri.reston.va.us]On Behalf
> Of Internet-Drafts <at> ietf.org
> Sent: Thursday, December 05, 2002 6:22 AM
> To: IETF-Announce:
> Cc: simple <at> mailman.dynamicsoft.com
> Subject: I-D ACTION:draft-ietf-simple-presence-08.txt
> 
> 
> A New Internet-Draft is available from the on-line 
> Internet-Drafts directories.
> This draft is a work item of the SIP for Instant Messaging and 
> Presence Leveraging Extensions Working Group of the IETF.
> 
> 	Title		: A Presence Event Package for the Session 
> Initiation 
>                           Protocol (SIP)
> 	Author(s)	: J. Rosenberg
> 	Filename	: draft-ietf-simple-presence-08.txt
> 	Pages		: 26
> 	Date		: 2002-12-4
> 	
> This document describes the usage of the Session Initiation Protocol
> (SIP) for subscriptions and notifications of presence. Presence is
> defined as the willingness and ability of a user to communicate with
> other users on the network. Historically, presence has been limited
(Continue reading)

Cullen Jennings | 8 Dec 2002 22:46
Picon
Favicon
Gravatar

RE: RE: I-D ACTION:draft-ietf-simple-presence-08.txt


Sorry for the post without reading all the list - I see they were updated to
a new version after this announcement.

> -----Original Message-----
> From: simple-admin <at> mailman.dynamicsoft.com
> [mailto:simple-admin <at> mailman.dynamicsoft.com]On Behalf Of Cullen
> Jennings
> Sent: Sunday, December 08, 2002 9:44 AM
> To: simple <at> mailman.dynamicsoft.com
> Subject: [Simple] RE: I-D ACTION:draft-ietf-simple-presence-08.txt
>
>
>
> I'm confused - is it version 8 or 9?  all I can find is
> http://www.ietf.org/internet-drafts/draft-ietf-simple-presence-09.txt
>
>
> > -----Original Message-----
> > From: scoya <at> cnri.reston.va.us [mailto:scoya <at> cnri.reston.va.us]On Behalf
> > Of Internet-Drafts <at> ietf.org
> > Sent: Thursday, December 05, 2002 6:22 AM
> > To: IETF-Announce:
> > Cc: simple <at> mailman.dynamicsoft.com
> > Subject: I-D ACTION:draft-ietf-simple-presence-08.txt
> >
> >
> > A New Internet-Draft is available from the on-line
> > Internet-Drafts directories.
> > This draft is a work item of the SIP for Instant Messaging and
(Continue reading)

Sudipta Ghosh | 9 Dec 2002 07:31

msgr

Hi,
MSN Messenger uses "msgr" tag in MESSAGE Request.
What is that?
sudipta

Example

MESSAGE sip:10.140.13.149:5060 SIP/2.0
Via: SIP/2.0/TCP 10.140.13.149:5060
Record-Route: <sip:10.140.13.149:5060;maddr=10.140.13.149;transport=tcp>

Via: SIP/2.0/TCP 10.140.13.96:11138
From: "Client_A"
<sip:Client_A <at> 10.140.13.149>;tag=65056eff-f536-43dc-a795-947be959f714
To:
<sip:Client_B <at> 10.140.13.149>;tag=f6dfc966-ad80-4cea-b8bd-ce3de259b79a
Call-ID: 89ef0faf-574f-4241-8a0f-9a3e4490a075 <at> 10.140.13.96
CSeq: 4 MESSAGE
Route: <sip:10.140.13.178:12155;transport=tcp>
Contact: <sip:10.140.13.96:11138;transport=tcp>
User-Agent: Windows RTC/1.0
Content-Type: text/plain;
charset=UTF-8;msgr=WAAtAE0ATQBTAC0ASQBNAC0ARgBvAHIAbQBhAHQAOgAgAEYATgA9AE0AUwAlADIAMABTAGgAZQBsAGwAJQAyADAARABsAGcAOwAgAEUARgA9ADsAIABDAE8APQAwADsAIABDAFMAPQAwADsAIABQAEYAPQAwAA0ACgANAAoA

Content-Length: 18

--
***********************************************
System Executive
Scicom Infotech Pvt. Ltd. (Scicom)
(Continue reading)

shanti | 9 Dec 2002 15:06
Favicon

SIP MESSAGE with MSN

hi,

When I send a SIP MESSAGE request to MSN client, it responds with 200 ok but
doesnot display the message .

Following is the message am sending, and the response received from the MSN
client.

MESSAGE sip:kviswa <at> abc.com SIP/2.0
CSeq: 1 MESSAGE
Call-Id: 1039218960404
From: <sip:sk_test <at> xyz.com>;tag=1093
To: <sip:kviswa <at> abc.com>
Via: SIP/2.0/UDP 192.168.123.159:2000
Content-Type: application/text-plain
Contact: <sip:sk_test <at> 192.168.123.159:2000>
Content-Length: 18

Hello

Thread-5:----------------------------------------
Thread-5:from = 127.0.0.1:3883
 to = 192.168.123.159:2000
 message = SIP/2.0 200 OK
Via: SIP/2.0/UDP
192.168.123.159:2000;branch=z9hG4bKad3693a4af1fd0c172f5a3cd2da61f43
From: <sip:sk_test <at> xyzcom>;tag=1093
To: <sip:kviswa <at> abc.com>;tag=156b140c-b8bc-431c-8416-467ef5b4c6f8
Call-Id: 1039218960404
CSeq: 1 MESSAGE
(Continue reading)


Gmane