Registration for SIPit 25 closes this Friday. If you plan to attend and haven't registered, please do so now. Information about the event and a link to the registration website can be found at http://www.sipit.net RjS
Please note the 18 September deadline for nominations. The NOMCOM will appreciate all the nominations it can get(Continue reading)Thanks! Ben. Begin forwarded message: > From: Mary Barnes <mary.barnes <at> nortel.com> > Date: August 31, 2009 5:23:03 PM CDT > To: IETF Announcement list <ietf-announce <at> ietf.org> > Cc: ietf <at> ietf.org > Subject: Nomcom 2009-10: Reminder Call for Nominations, Local Office > hours, Nominee Questionnaires available > > Hi all, > > This email covers 3 topics: > 1) Reminder: Call for Nominations > 2) New: Local Office Hours > 3) New: Questionnaires available for nominees > > Best Regards, > Mary Barnes > nomcom-chair <at> ietf.org > mary.h.barnes <at> gmail.com > mary.barnes <at> nortel.com > >
This is a _repeat_ WGLC for comments on http://tools.ietf.org/html/draft-ietf-simple-intradomain-federation-04 . We did not get sufficient comments the first time around. Please send your comments to the editor and the list by 5 October, 2009. Even if your comment is "The draft is okay", that's helpful. Thanks, Ben. Begin forwarded message: > From: Ben Campbell <ben <at> nostrum.com> > Date: August 18, 2009 3:13:03 PM CDT > To: Simple WG <simple <at> ietf.org> > Subject: [Simple] WGLC: draft-ietf-simple-intradomain-federation-04 > > Folks - > > This is a Working Group Last Call for comments on > http://tools.ietf.org/html/draft-ietf-simple-intradomain-federation-04 > > The editor believes this draft is ready to last call, and we did not > have objections to doing so in the Stockholm meeting. > > Please have your comments to the editor and list by 2 September, 2009. > > Thanks, >(Continue reading)
http://wiki.icanblink.com/ Blink implements RTP audio sessions (VoIP), session based Instant Messaging (IM), File Transfer and multi-party chat sessions using MSRP protocol and its relay extension, desktop sharing using VNC protocol, publication and subscription for rich presence information such as availability, moods, activities and geo-location, management for the presence rules, resource lists, RLS services documents using XCAP protocol. You can receive a notification when the software become available or participate to our early adopter program by registering on the mailing list: http://lists.ag-projects.com/mailman/listinfo/blink The software implements most of the SIP SIMPLE working group items and will have an open source license. -- Adrian
2009/9/28 Adrian Georgescu <ag <at> ag-projects.com>: > http://wiki.icanblink.com/ > > Blink implements RTP audio sessions (VoIP), session based Instant Messaging > (IM), File Transfer and multi-party chat sessions using MSRP protocol and > its relay extension, desktop sharing using VNC protocol, publication and > subscription for rich presence information such as availability, moods, > activities and geo-location, management for the presence rules, resource > lists, RLS services documents using XCAP protocol. > > You can receive a notification when the software become available or > participate to our early adopter program by registering on the mailing list: > > http://lists.ag-projects.com/mailman/listinfo/blink > > The software implements most of the SIP SIMPLE working group items and will > have an open source license. Let me a question. After studying all the SIMPLE and XCAP stuff (and implement part of it), I get a simple conclusion: XCAP and SIMPLE specifications *don't* exist. With it I mean that SIMPLE and XCAP (as specified by IETF) don't provide a fixed and strict set of rules and specifications and it's *impossible* to get interoperability. Some examples: - RFC 5025 (pres rules) doesn't specify which is the default action to perform is a watcher URI is not listed in the document. - RFC 5025 doesn't clarify which should be the presence server(Continue reading)
2009/9/29 Iñaki Baz Castillo <ibc <at> aliax.net>: > So, what we have? nothing. We have a hyper-complex and ambiguous set > of specifications which don't provide interoperability at all. When I > read "this softphones implements XCAP" I understand "this softphone > implements XCAP so it works ONLY with same vendor's softphones, XCAP > server and presence server". Is this what we want? > > OMA's XDM specification is a specification layer on top of XCAP/SIMPLE > documents which tries to create a fixed and strict subset of IETF > specifications in order to make it feasible for clients adoption. For > example it defines a very strict format for the pres-rules document. > It also defines the XCAP server behavior (XDMS server). > > I really think that this should be a task of IETF rather than OMA. I > cannot understand why IETF has published such useless and half-done > documents, can I ask *why*?? sharing a simple budy list or privacy > rules is IMPOSSIBLE with IETF's specifications!!!. Anyhow this is what > we have. > > Which should be the way to go? perhaps implement OMA's XDM specs? > (I've read XDM documents and they are designed to be SIP core agnostic > (valid for IMS or any kind of SIP core). > > > Sorry for this mail, but this subject is really depressing for me. Of course, I really appreciate the effort AG-Projects is doing in SIP presence stuff, really amazing! -- --(Continue reading)
Dear IETF colleagues,the recently-sent LS below did not appear on the SIMPLE mailing list.This is another attempt (with the attachment converted to PDF) to get it through.OMA kindly asks the SIMPLE working group to address the issue reported in the enclosed LS.Kind regards,
Uwe Rauschenbach--
Dr. Uwe Rauschenbach
Senior Specialist
Nokia Siemens Networks GmbH & Co. KG
Research, Technology & Platforms
St.-Martin-Str. 53, D-80240 Munich, Germany
Tel.: +49 89 5159 29751
Mobile: +49 173 3083573<OMA-LS_834-ARC_and_MWG_to_IETF_on_XML_validation_issues-20090923-A.pdf>From: ext Louise Clarke [mailto:Louise.Clarke <at> forapolis.com]
Sent: Wednesday, September 23, 2009 9:52 AM
To: dean.willis <at> softarmor.com; adam <at> nostrum.com; simple <at> ietf.org
Cc: OMA-PLENARY <at> MAIL.OPENMOBILEALLIANCE.ORG; OMA-LIAISON <at> MAIL.OPENMOBILEALLIANCE.ORG; UNMEHOPA, Musa (Musa); Rauschenbach, Uwe (NSN - DE/Munich);kyungtak.lee <at> samsung.com
Subject:
To: IETFCc: OMA-TP, OMA-Liaison, ARC Chair, MWG ChairDear IETF,Please find attached a Liaison Statement from OMA Architecture and Messaging Working Groups on XML validation issues for your considerationKind RegardsLouise ClarkeDocument Support OfficerOpen Mobile AllianceTel: +33(0) 492 944912Mob:+33(0) 607590853
<<OMA-LS_834-ARC_and_MWG_to_IETF_on_XML_validation_issues-20090923-A.zip>>
_______________________________________________ Simple mailing list Simple <at> ietf.org https://www.ietf.org/mailman/listinfo/simple
RSS Feed2 | |
|---|---|
2 | |
12 | |
14 | |
1 | |
68 | |
128 | |
63 | |
7 | |
9 | |
13 | |
22 | |
3 | |
36 | |
47 | |
14 | |
7 | |
22 | |
26 | |
66 | |
53 | |
50 | |
205 | |
161 | |
33 | |
16 | |
13 | |
24 | |
56 | |
87 | |
42 | |
39 | |
5 | |
3 | |
19 | |
49 | |
60 | |
25 | |
27 | |
35 | |
57 | |
52 | |
30 | |
6 | |
23 | |
51 | |
15 | |
31 | |
95 | |
58 | |
39 | |
8 | |
12 | |
50 | |
27 | |
31 | |
22 | |
39 | |
22 | |
36 | |
24 | |
93 | |
42 | |
74 | |
38 | |
54 | |
34 | |
35 | |
101 | |
80 | |
33 | |
50 | |
38 | |
71 | |
55 | |
32 | |
27 | |
30 | |
101 | |
32 | |
56 | |
121 | |
67 | |
74 | |
73 | |
160 | |
111 | |
64 | |
60 | |
115 | |
103 | |
44 | |
110 | |
113 | |
127 | |
20 | |
65 | |
177 | |
171 | |
144 | |
110 | |
168 | |
316 | |
144 | |
170 | |
149 | |
3 | |
8 | |
36 | |
114 | |
7 |
